>>>>>>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.
>>>>>
>>>>>Try temporarily renaming your FOXUSER.* files, see if that makes a difference.
>>>>
>>>>Didn't work
>>>
>>>You're certain you renamed the correct ones? In other words you saw new ones created in the same folder?
>>
>>Al:
>>
>>Now I'm really lost. It appears that my VFP is not using foxuser. The one I renamed is from 2 weeks ago and I did a search of the entire network and there is no foxuser that has been updated today. How does this work?
>
>Perhaps you have a CONFIG.FPW file in effect, and it contains RESOURCE=OFF ? Is there any SET RESOURCE OFF or SET DEBUG OFF in your code?
>
>Do you have full privileges in the folder that contains your FOXUSER files? Have they somehow been set to read-only?
>
>Does SBT do anything funky with custom resource files or DEBUG settings?

There are a whole bunch of CONFIG.FPWs on the drive, all with RESOURCE=OFF. I commented that line out, but it seems SBT is setting it off somewhere in its code, because I see in the debugger that set('Resource') is OFF. I'll try and play with this later, but any information would be helpful, such as:

1. Which CONFIG.FPW is the operative one?
2. Once I turn RESOURCE=ON, at what point is a new FOXUSER created?
3. Why is this my debugger problem?

Thanks,

Yossi