>>>But, for the sake of progress, let's agree that it is a "bug" in one's own code. Why does it try to "help" me in such a useless way??? Why doesn't it do as it does with countless other conditions that may arise because of MY logic errors - raise an EXCEPTION????
>>
>>It makes sense to me if I look at it this way. I am testing my app. I forgot to open a file. VFP is giving me the chance to open the file with a dialog. I could just quit the app at that point, fix it in code, and start testing from the top again - or - I could designate a file in Ope dialog, and continue testing - and fix the open error later.
>
>If it was a setting, you could still have it that way, or even if you Set FileOpenDialog OFF, you could have your error handler know you're in development, let you suspend, open the file manually, take note and continue the run.

It's a hard call. Maybe it's Pavlovian technology! You know, like negative reinforcement (that's skinner - hmmm). Anyway - some MS- VFP conference call decided:"If the developer is doofis enough to request a nonexistent resource, we hurt him - ya see! Hit him hard. Hit `em low! Ya see! It won't be long fore he gets his arse back on track and quits doing this stuff."

Pavlov could be applied subsequent to reinforcement therapy (ie: the "Open" dialog). Before committing a single word to a select statement, the developer will grind teeth and sense despair for 1.5 seconds. This will remind said developer that "no one" fools with mother soft's Watson interface. NO ONE! Open your file first - OR learn what pain really is!:-)

It's a scheme - a conspiracy - a play on our sensitivities. We are hive. We are controlled by aerosoled releases of mother soft's pheromones! Resistance is futile! DEAL WITH IT:)

... and that's why i don't do two shows a night!