Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Debugger demands a table
Message
From
19/03/2000 20:06:36
 
 
General information
Forum:
Visual FoxPro
Category:
Conferences & events
Miscellaneous
Thread ID:
00347178
Message ID:
00347689
Views:
27
>>>Hi Ed,
>>>
>>>>The most likely cause is that you've left a value in your Watch Window that expects to act on a table when you last exited from the debugger - go into your FoxUser file and delete all the relevant records - the WATCHEXPR record contains the current values set in the Watch Window.
>>>
>>>Any idea what value would do that? When I tried to duplicate the problem, I tried putting alias.field, RECCOUNT(), DBF(), and none of them caused a file prompt -- they just showed blank or "cannot be evaluated".
>>
>>
>>Good question. I even tred the obvious ones like "USE ?" or "BROWSE" and they just gave me the "expression cannot be evaluated" message.
>
>We got our answer - an AFIELDS(). I can't imagine dropping that in a Watch window; it'd return the number of fields in the CWA each time, and repopulate the ref array...I'd expect VFP to fall down go boom in short order!

I tried AFIELDS() after I read that message. I still only get the "Expression can not be evaluated", no prompt for a table.
Fred
Microsoft Visual FoxPro MVP

foxcentral.net
Previous
Reply
Map
View

Click here to load this message in the networking platform