>>>>Hi All:
>>>>
>>>>I have the following annoying bug in the debugger: Sometimes the arrow stops a few lines before the actual line that it is executing, so that as I step thru the code, it is actually executing a few lines later. This makes debugging very frustrating. If this is a bug in 5.0, then there is nothing I can do. However, is there a solution to this?
>>>>
>>>>I even tried to completely rewrite the source code in case the file was somehow corrupted, but it did not help.
>>>>
>>>>As usual, the following: My client is using SBT 5.0 which runs under VFP 5.0, has no intention of upgrading and for the most part this is fine with me.
>>>
>>>I've seen this over the years and in many different versions. Typically, when I see it, it's the Debugger stopping on the line before the one where I have the breakpoint. I've never figured it out, just live with it.
>>>
>>>However, what you're describing isn't what I'm seeing. You seem to be saying that the arrow isn't pointing to the line of code it's executing. I see the arrow in the right place; it's just not stopping where I wanted it to.
>>>
>>>Tamar
>>
>>The arrow is pointing 5 lines before the line that is about to be executed
>>
>>So:
>>
>>

>>Line of code  <<=== debug arrow
>>
>>Line of code
>>susp
>>
>>lcVar1 = 'cat'   <<=== the debug arrow should be here
>>lcVar2 = 'dog'
>>

>>
>>In the above, the watch window shows lcVar1 and lcVar2 as undefined.
>>
>>Now I press the step button and this is what happens:
>>
>>

>>Line of code  
>>                     <<=== debug arrow
>>Line of code
>>susp
>>
>>lcVar1 = 'cat'   
>>lcVar2 = 'dog'  <<=== the debug arrow should be here
>>

>>
>>In the above, the watch window shows lcVar1 = 'cat' and and lcVar2 is undefined.
>>
>
>That, I've never seen.
>
>Tamar

Sigh. I'll just live with it.