>Hi Stephane, how are you?
>
>If I am understanding this correctly, it's VFP popping an Open box when it can't find a DBF that is the objection. Hmmmm....
>
>I can try to raise an ER, but this behavior is so endemic to a lot of the product that I'm not sure it'd go anywhere.
>

Hiya Gonz,

I may not be the best one to explain it but here's the issue...

If an SQL statement is issued with a table with the alias indicated in the FROM clause not being opened, the open file dialog appears without any indication of what file is being selected from. In some ways I can understand the behavior. Afterall, the primary portion of the file name may or may not be the alias referenced.

What's being requested is that a switch (most likely a SET command) be implemented so that the dialog doesn't appear and an error raised.

Personally, I wouldn't vote on this wish as I always open the necessary files prior to issuing the query. I feel that this gives me more information to help resolve the problem if the file cannot be found and so on. My open table routine can log both the fully qualified file name and the alias, rather than just the alias alone. In my mind, this can help me resolve the problem more quickly.

I have a number of tables with the same structure that a single query is run against. Knowing just the alias in this instance means that I have to check all the possible tables in order to assure that this is resolved. With the actual file name, this step is totally unnecessary.