Hi Gary,

>Sure, you can USE the table in the AfterOpen but why not just use a standard CM cursor object just like any other table? All you have to do is set it up just like a table in a DBC where cType == "Table", cDatabase == '' (None in the property window) and cSource is the free table name. If the free table can be found along your path, just the name of the table will do (you don't even need to specify ".dbf"). Other than that you can specify a path and filename in cSource but obviously, this can be a problem if the file may be in a variable location "on-site".<

There are a couple of somewhat unusual things that I am having to do in this situation. First of all, the Table does not always exist when the app or even the form for that matter is started. For "some but not all" users I am creating a free table (which I do using the Copy to with CDX command with a fields list) to a special folder on the local workstation. Then, I need to be able to also use this free table in the List lookup dialog. I still haven't been able to get it to work correctly (the only problem is when the dialog is closed, it doesn't remember what column was selected the prior time it was open).

To try to track down what the problem might be, I even created a copy of the free table and put it in the Local folder, and then added this table to the CDE so that it's opened with the other tables found in the CDE when the form is opened. It still doesn't remember that last column used setting.

I have the List dialog working correctly everywhere else, but it just seems to be causing a problem dealing with this free table.

Thanks for your help.

Mel Cummings