Hey Steve,
I'm with you on this one. If a user is prompted to open a table in any of my apps then an error has occured (in this case due to poor design, a bad day, or plain stupidity on my part) and I need to trap for it.

I imagine there are probably apps out there though in which programmers have allowed for the enduser to select a table when a select statement is issued and like it fine the way it is...maybe they provide a premessage as to which table to search for? Hmmmmmm, seems they would do that before issuing the select statement though, ok I can't think of any reason for it to behave the way it does!

Update: However, I also agree with Renoir. I did understand him, I just couldn't figure out why he would want to do it! That made it more confusing. It's just me! :o)


>Hi Renoir,
>
>But some of us think it should be an error. What is the user supposed to do? Guess what file to open?
>
>If this dialog pops up, it is because there is a bug in my code. I would rather it go through the same route as any other error that may occur--through the error handler.
>
>Those are just my thoughts on the matter :)
>
>
>>Marc,
>>
>>I think most everyone understood you. They were just trying to help you work around it. A Foxpro error message looks very different than the open dialog box and I think everyone was wondering why you were trying to trap it as it was somewhat obviously not an error.
>>
>>Renoir
>>
>>>> VFP doesn't consider it to be an error.
>>>At last, someone understand me! Thank you.