>Hi Mark,
>
>I am glad for your advise, but I can not use that solution. Your solution would work had I been using the query wizard for myself. I am writing a program that will be ran by the QA department. One of the function that they want was to be able to query a table for whatever reason. I create a button among many to run the query wizard that will allow them to go thru the steps to built a query (the table structure can be modified, thus the need for alias name, because all fields of the table structure maybe not be needed for field comparison) and then store those results in table. They will not have access to a command line, and most QA person would not know what to do if they were there. When they save the query and it opens into the query designer - let will be require to select the output method (to table),save and run the query - it will generate an error because the table that is reference in the SQL(view) is no longer available (for other reasons stated above, it may have been
>modified), but the alias will be present. Thus I need a way around this problem without "MODI QUERY" command or any changes needed by "re-opening" the query file.
>
>Thanks in Advance for your help

OK, I now understand that. I want to try to capture the steps involved --

1. User opens Query Designer, creates a new query.
2. User runs query and it works this time. Output goes to report or table.
3. User then Saves and Exits Designer.
4. Some time later, a table's structure changes or a table is deleted.
5. User opens or runs a previously saved query but gets error because table was deleted or its structure changed?