Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
User-interface operation not allowed at this time. Why?
Message
From
25/11/2000 14:41:08
 
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Miscellaneous
Thread ID:
00443995
Message ID:
00445387
Views:
15
>Wouter,
>
>I did think of another thing while driving last night. USE will display a File Open dialog if the table doesn't exist. If the .fpt or .cdx do not exist other dialogs will display.
>

As a member of the people likely to fall into the 'stupid' camp, there's also the possibility that an error caught by the OS could be triggering a dialog from outside the VFP runtime itself; it's like the difference in behavior between Win9x and NT-derviced OS treatment of the 'Drive no ready' condition - WIn9x passes the error along to VFP to handle, while the default behavior of NT-derived environments is to pop a messagebox at the OS level rather than passing the error back to the app for handling, based on the setting of some OS-specific error handling behavior, and since the error is processed before VFP's error handler would ever have a chance to deal with it...

Just call me stupid!
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform