A mix of Autoamtion and CursorAdapter may be helpful here. We tried extracting data from Access through automation and found it much easier with a remote view. The CursorAdapter, to my understanding, operates much the same way as a remote view but not requiring the DBC host. Also the CursorAdapters properties may be assigned on the fly a little easier if you ask me.

In short I guess I'm saying that you can use Automation to discover the table names and such. Then use the gathered information to make the proper settings in a CursorAdapter. That will at least give you a native FoxPro cursor that should be much easier to manipulate.

Now that I'm thinking about it we may be able to use something like this at our company as we do a lot of data conversion. I will give it a go a little later today. I'll keep you posted on my progress.

Aloha,

James


>Thanks.
>
>My reason for not using ADO or ODBC connections which are required for CursorAdapter or Remote Views, is that the Access databases I need to access have unknown names and contain unknown tables. My code needs to find the Access databases, open them, find what tables they contain, and export the data into text files that my program's code will then import.
>
>So, I'm thinking I don't want to try to manage connection strings since all the database names and table names are constantly changing. Well at least let's say I don't know how to do that with code.
>
>Is it impossible to pass a constant to Access as it is expecting?
>
>Ps. I have a similar problem if I write the code in wscript.
>
>Thanks,
>Gaylen Miller