>>Am I correct - the dalog only appears when the programmer erroneously neglected to open a file before a select was issued?:0
>
>I know it also appears when a table is open with different ALIAS than code is looking for, that's when I usually see it in development.
>
>As I said elsewhere, I don't have a big problem with the curent situation either, as good, tight coding completely eliminates it. But still, it does seem like a relatively easy thing to do - just add the error-trap capability, I mean. The more we can trap, the better, is my attitude, I guess, as a general philosophy.

It seems like the process is suited for the command window interface than a runtime. But - it also offers an option. User production is stopped while waiting for repair, or second chance to manually locate the file with hope of continuing production until repairs are completed. You're right - it's a small potatoes issue - surprise is how deeply the issue seems to affect us:)