Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Form Differences: Runtime vs. Development Behavior
Message
From
13/01/2005 11:45:42
Spencer Redfield
Managed Healthcare Northwest, Inc.
Portland, Oregon, United States
 
 
To
13/01/2005 10:12:28
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows NT
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00976498
Message ID:
00976817
Views:
9
Thank you very much for your kind help and ideas.

1) I have double-checked and can verify that the “problem” form is indeed modal. This according to my test WAIT WINDOW message and viewing the property sheet.

2) I double-checked the error handling in this “problem” modal form. It is a simple
* Note:  …. indicates more in the actual expression
on error messagebox( program() + chr(13) + message() + chr(13) + …..) 
I then purposely introduced a syntax error in the form’s INIT event. When run, the ON ERROR messagebox appears appropriately. Hence I’m pretty much comfortable in ruling out the above ON ERROR command itself as the cause.

I would like to re-ask the question, have others ever observed distinct and unexpected differences when running the same .EXE from the command line vs. as a standalone .EXE? I mean, is this even conceivable?

Thanks again,

Spence
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform