#Do While improper end
9 messages in this thread
In one of my programs the Do While completes and exits the procedure, but
instead of exiting, it returns to the last DO While for another pass. Has
anybody run into this?
Thanks,
Phil
There are 2 Replies.
Philip,
You might want to take another look at your message. It's not exactly clear
what the problem is.
Can you give us an example of the actual code you're using?
Mark
Hi Philip,
Can you create a code snippet that would show this problem about the
DO…WHILE problem you are having. I'm sure that there is some program
logic. I have never heard this problem before.
Don Funk
There is 1 Reply.
Problem is random – about 1 in 10 to 1 in 5 times and only when you
first start the program. It looks like some kind of uninitialized variable
within VB for handling loops or a stack handling problem with VB. I'll try
to isolate this to a minimum amount of code. If I could get Assembly
Output I could figure out what the machine is doing.
There is 1 Reply.
I don't think that ASM output would help you. VB is a PCODE interpeter.
Your best bet is to include the routine so we can see exactly what you have
typed in.
As speculation, it could be that your routine is exiting the sub, but is
being thrown back in by the calling routine…Include both.
– Ricks
There is 1 Reply.
The strange thing is that it gets thrown back in at the point of the
beginning of the DO LOOP not at the beginning of the SUB. Is there
a P Code debugger/disassembler to allow viewing of the P Code machine?
There is 1 Reply.
None that I know of!
– Ricks
Boy, that's great – the environment is unreliable (looks like stack
corruption). The only unusual thing about my application is that I am
doing communication in the background. But at the point where this error
occurs, there is no communications going on.
I am now getting UAEs from the environment when running the program on a
286 machine.
I've got to say that while VB looks good, it does not appear to be stable
or worthy of use in a mission critical application.
There is 1 Reply.
Philip,
If you were programming in C or Pascal, I would sure suspect a renegade
pointer somewhere! Are you, by chance, using DLLs? If so, you might be
passing an incorrect parameter type, or an uninitialized string.
Just for laughs, zap the background communications and most, if not all
other software, while doing some thorough tests. This will eliminate them at
least.
I have had a *few* problems, but not to the degree that you have experienced.
Before making the final decision on the reliability of VB, you might want to
write another app.
Personally, I use VB for small-medium size projects and use TPW for
medium-large "workhorse" projects. Maybe that's why I haven't run into your
problem.
– Ricks