Hi Sergey

You were right, it was foxuser.dbf.

The registry holds a pointer to the current foxuser.dbf, which it would appear it loads when VFP is executed. In this case it was on a totally different network drive to the system I was working on.

The foxuser.dbf table was 388K which is the biggest I've seen.

Thanks for the help.

I wonder if that fixes my AutoOpenTables problem????

Regards
Geoff Scott

>In the development set where debugger doesn't work properly. The info you're talking about is stored in the foxuser.dbf.
>
>>Hi Sergey
>>
>>Which one. There is one in each development set I have.
>>
>>There must be a generic config somewhere that remembers where one has been etc. probably in registry
>>
>>>>Hi
>>>>
>>>>I have a major problem with my debugger under VFP 7.0. It doesn't fire when it hits a breakpoint.
>>>>
>>>>The problem seemed to arise after I was woring with two instances of VFP both with instances of the debugger.
>>>>
>>>>Has anyone experienced this and if so how did they fix it???
>>>>
>>>
>>>Try to delete foxuser.dbf.