>>Have you even SEEN which dialog we're talking about here Terry. You seem to think it is the GETFILE() dialog. It is not! It simple has "Open" in the title bar and has buttons OK and CANCEL. No file name, NO user-discernible info AT ALL!!!
>>
>Don't view it as an OpenFile kind of dialog. View it as an error message - thats what it is - it would not have popped unless there was a logic bug in the code - right?

No - you are fixated on BUG. Have you not read others replying to you that tried to show how external things can happen that there is NO program control over??
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????

That's all people are asking for. Then we can ALL be happier with VFP.
Keep in mind, too, that the current situation has extra implications in the non-English speaking world, making the dialog even more evil than for us folks here.

Jim



>
>>>
>>>I have a hard time understanding why many of us are SELECTING from DBFs. Typically, when we do that, we bloat the CDX (I've seen an index on every field). SEEK is lower level- seek is faster - seek does need a result cursor - and when planning an app using seek, the discipline seems to force more normalicy and optimization - plus - we don't have to index on every field!
>>
>>Fine, that's YOUR style. But the fact of the matter is that you are one of the minority who did not go for the big MS/VFP push to move to SQL styled processing some time back.
>>
>Have you ever noticed, just a small minority of VFP apps have sex appeal?:)
>
>>Jim
>>SNIP