FWIW, it causes the same behavior on Win2K SP2.

Because of the dynamic nature of the Watch window, using Sys(3096) directly causes an error. If you want to examine this information, set variable to the return values and add them to the Watch window (it does not throw an error).

In addition to SET RESOURCE OFF, you could have used CLEAR DEBUG. This would have set all Debug windows settings back the the factory defaults with no Watches set up.

>This is something happened to me while testing some of the new VFP7 functions
>
>I wrote as a watch expression the following:
>

>SYS(3096, SYS(3095, _VFP))
>

>
>It said:
>

>(Expression cannot be evaluated)
>

>Fine...
>
>I use resource file, my debugger windows are docked, running VFP7 english version under Win98SE.
>
>when I have closed the debugger window, and tryed to reopen it - it closed automatically together with my VFP main window
>
>Restarted VFP...
>

>DEBUG
>

>the same...
>restarted VFP ... tools-debugger - the same, after OS restart - again the same.
>
>:(
>'Should I reinstall VFP after this?' I've asked myself
>No... for my happyness :)
>
>I've turned off the resource file (tools-options-file locations ... )
>started debugger (it looked ugly - however I was able to see it :) )
>after that (without closing the debugger)
>turned on the resource file...
>and voila it is now working...
>
>Any ideas why it happened?
>I know that it is an undocumented 'feature' in VFP7 :o)
>Pay less - get more! :o)