Printable View
I have a VB 6.0 application and it runs really good. However, there is an instance.. say one out of 100 times when the application freezes. It does not affect the system (win 2000) though and the user can still click the X in the corner and exit the application and start it up again and everything is fine.
Is there something that could be causing this?
VB isn't my forte but I know that in most programming languages, this sort of problem is often caused by uninitialised variables - i.e. most of the time, the variable happens to initialise to a value that does no harm, but every now and then....
In Visual C++ (which I use) the compiler throws up a warning if a variable is used without being initialised. I don't know what the situation is with Visual Basic - but the warnings aren't infallible anyway. You might just need to take a good, hard look to see if any varables are being used before they've been set to a sensible value.
VB doesn't require variable intialization.....did you try a debug stream or merely parsing out the suspect code with return statmenet to at least isolate the problem? It often is a memory issue!
So what would happen if someone did this:-Quote:
Originally posted by mikedershowitz
VB doesn't require variable intialization.....
That kind of thing would probably cause an unexpected result in most computer languages.Code:Dim intXXX As Integer
Dim intYYY As Integer
intXXX = CallSomeFunc(intYYY)
I cannot get the problem to recreate when I am running it in development mode in VB. It only happens after I install it on a PC. I do not know the area of code that is suspect. Is there a way that I can debug after an install?
We well, I realized that the program does not actually freeze cause i can actually select something else to do. I can even select the same option again. It again does nothing. But the form still seems active.
anyideas are welcome. My release date is today