>>Now what I'd like (i.e. I'm with Fabio on this one) is to have error 52 ("No table is open in the current work area.") happen immediately, without showing the file open dialog... so
>>
>>Set Fileopendialog Off
>>
>>...is what I'd like to see. With a shorter name, though :).
>
>I agree too, this might be a medium-level wishlist item. I've only had it occur in development for the past few years, since I've learned to avoid it with tight code, but this shoudln't be so critical as it is to code for, IMO.
>
>I might add that since I often use different aliases for tables than the actual name (so multiple exact-same-structure tables can use same code), the open dialog does not offer ANY useful solution even if you're in development mode, let alone some poor user faced with the Open screen...
>
>However, as a "devil's advocate" I might mention that I've hit these SQL -"table-not-found" situations in PB/Sybase-Oracle apps, and they simply crash, after some bizarre, huge & unuseful (to user) error message, when a table could not be found...

What's the favorite sentences that American mothers use when they tell their children not to use worse than themselves as role models?

I agree, this is not a huge bug, but when it happens, it's annoying - and the reason it's annoying is that the error is not caught before the user sees anything, which makes us look sloppy. And our tool is the best. Once this is fixed, it will be perfect :).