|
What do you mean ?
Christian Graus
Driven to the arms of OSX by Vista.
Please read this[ ^] if you don't like the answer I gave to your question.
"! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
|
|
|
|
|
In vista Microsoft Defender shows my application is shows
Digitally Signed By: NOT SIGNED
Microsoft application shows it
Digitally Signed By: Microsoft Windows Verification PCA
so how to set digital sign for my application.
If you can think then I Can.
|
|
|
|
|
You have to purchase a certificate from a third party company. Try googling Thawte or Verisign and taking a look at their websites. They have a lot more information on the topic.
|
|
|
|
|
I am trying to built the certificate for my softwares. Not Certified by Verisign or Microsoft CA etc.
We are developer pls give me the way for developing that.
Thanks
If you can think then I Can.
|
|
|
|
|
You have to purchase a digital signature from a certificate authority such as Verisign or Microsoft CA. You cannot develop it in-house if you want it to be certified by Microsoft. This is good; if virus-writers could do this, they could masquerade as a Microsoft-certified application. They would be trusted by users and allowed to run all over the system
Between the idea
And the reality
Between the motion
And the act
Falls the Shadow
|
|
|
|
|
Thanks for Help.
If you can think then I Can.
|
|
|
|
|
Hello everyone!
If we change the language from Regional Settings of Windows XP. Most specifically changing "preferred language" under standards & formats tab of Regional Settings dialog.
Now tell whether VB6.0 uses the same "User Default Locale ID" language for running applications using IDE? As When I run my application from Visual Studio 6.0 I get results in User Default Locale ID language or preferred language (as stated in first paragraph above). But after creating EXE of the application I get System Default UI Language.
Please tell me the standard rule VB6.0 uses.
Thanks.
Be Happy.
modified on Wednesday, June 3, 2009 2:43 AM
|
|
|
|
|
hi
i am using microsoft office (old version) excel visual basic editor.
currently i am stuck as i am trying to change the events of my form.
like form load, (top right corner of the form) close button and such
does anyone know how this can be done>?
as i understand in visual studio and such it is possible.
|
|
|
|
|
You cannot change the events inside Office. You just have to use what's exposed and understand that there is vast differences between Form events in a VB6 or VB.NET app and the events you find for UserForms in Office.
|
|
|
|
|
is there a way to disable it then? or attach an additional event to the close button?
|
|
|
|
|
Disable the close button?? Nope. You just have to be very clever in the way you handle the form being closed.
|
|
|
|
|
I have to fix a defect raised for an old legacy VB6.0 application. I am seeing really weird behavior when subtracting two double values.
I have two double variables. d = 2.3434543434E+15 and d1 = 2.3434543434E+15 . Both have same values. Weird thing is, d1 - d gives me 2 instead of 0! Just to see where I am going wrong, I ported this piece of code to C# and everything worked fine there. If I do d1 / d , I am getting 1 in VB which is correct. But what's wrong with the subtraction?
Any ideas?
|
|
|
|
|
Hi,
there most likely is nothing wrong. Have a look here[^].
It is inherent to floating-point numbers: they trade some accuracy for a much larger range.
A floating-point number stores a mantissa, an exponent and a sign.
the exponent indicates a power of 2, not 10, and uses anywhere between 8 and 16 bits.
the mantissa indicates a magnitude in a limited range, say in [0.5, 1) and uses some 23 to 50 bits
(details vary from one CPU family to the next, IEEE did some standardization attempts, not relevant here).
You have chosen to show the number as d = 2.3434543434E+15, now why didn't you chose d = 2.343454343411111111111E+15? I added some ones to emphasize that you stopped the representation hoping the decimal digits shown, exactly correspond to the binary bits present in the mantissa, which will not be true in general.
So one number could be 2.343454343411116E+15 whereas the other could be 2.343454343411114E+15 (I truncated where the decimal point would be when looking at integer values). So now the difference is exactly 2, whereas the quotient is 1 + epsilon, epsilon being a very small number (around 1/1.17E15);
a double would be able to hold epsilon very accurately, however 1+epsilon would not be discernible from 1.
It is a well known fact in numeric analysis subtracting two large and similar numbers increases the relative errors. Example: if you want to measure the thickness of a wall, you could measure the wall-to-wall distance of a room on the inside, do the same on the outside, and subtract. If you make a 1% error on those dimensions, your calculated wall thickness could be off by 10% or more.
If you want to see the details, try to have a look at the bit patterns used by d1 and d2; in .NET BitConverter.GetBytes() would give you access to them, I don't recall if and how it could be done in ancient VB.
A much simpler example illustrating the same principles would be to calculate 1/3 or 1/7, then multiplying again by 3 or 7; the result will not always be 1!
PS: the above is true in many/all programming languages; some do offer extra data types (such as decimal) to get yet another trade of of accuracy and range.
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get.
Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
|
|
|
|
|
You really ARE the man, Luc! I very much enjoy reading your responses...
|
|
|
|
|
Ditto to that! Almost like Luc knew something about big numbers
"There's no such thing as a stupid question, only stupid people." - Mr. Garrison
|
|
|
|
|
big numbers don't fit in a double.
I have been busy creating my own BigInteger library, where arbitrary length integers can be stored and operated upon. Got somewhat stuck on efficient division and square rooting, and now .NET 4.0 is finally offering such class.
FWIW: we humans don't know any big number; whatever number we come up with, it is always part of a really tiny miniscule fraction of the numeric universe, almost all existing numbers happen to be larger... and less popular.
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get.
Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
|
|
|
|
|
Thanks Luc. That was a mind blowing answer. A well deserved 5.
|
|
|
|
|
you're welcome.
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get.
Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
|
|
|
|
|
I have done some more analysis with other languages. Here is what I found,
double d1 = 2.343454343411114E+15;
double d2 = 2.343454343411116E+15;
double sub = d2 - d1;
double div = d2 / d1; In C++ (compiled with gcc on LINUX) gives sub = 2 and div = 1 . In C# the same code gives sub = 2 and div = 1.0000000000000009 .
|
|
|
|
|
Hi,
on the same hardware, one would expect identical results, except for one thing: when you let the code show a floating-point value without specifying explicitly how many digits should be shown, then (the designers of the run-time library of) some languages may choose to show as many digits as are likely to be significant (e.g. always 16 digits, possibly truncating all the zeroes to the right), while other languages might choose to show a much lower number of digits by default (trying to show "rounder" numbers, i.e. hiding the anomalies to some extent).
Most languages also allow explicit specification of the output format (as in %22.16d in C); when such is done equivalently in different languages on the same hardware, I would expect the results to be identical.
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get.
Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
|
|
|
|
|
hi everyone .. well i am truing 2 make a button when i click it would truncate the data in table , i am trying 2 do this by vb.net 2005.
so if anyone got the code or an example 4 it would b nice .
thanx 4 all.
|
|
|
|
|
Firstly you will need to define what you mean by truncate.
Secondly you need to show the code that you have tried, together with details of where it fails, and any error messages.
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
|
|
|
|
|
ok , first i want to clear all data in specific table in sql2005 data base , and i need 2 execute the order " truncate table xxxxx " not from the sql query analyzer , but from vb.net code , which i am trying 2 make here :
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim strSQL As String
strSQL = "TRUNCATE TABLE names"
Using connection As New SqlConnection(constring5)
Dim command As New SqlCommand(strSQL, SqlConnection1)
command.Connection.Open()
Command.ExecuteNonQuery()
End Using
End Sub
it gives me error message in code
command.Connection.Open()
<b>"The ConnectionString property has not been initialized."</b>
so i dont know what i should do
thanx
|
|
|
|
|
OK.
Using connection As New SqlConnection(constring5)
Dim command As New SqlCommand(strSQL, SqlConnection1)
this is where I suspect your problem lies.
In the first line you set up connection , then in the second line, instead of using connection you use SqlConnection1 . Why? Try replacing SqlConnection1 by connection .
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
|
|
|
|
|
thank you
|
|
|
|