After thinking about this a little more, it occurred to me that the best way to connect to a DBC and a DBF is to create a remote view for the DBF inside the DBC. You will still use two data adapters, but everything will go through one OleDbConnection. And that allows you to use transactions to preserve the atomicity of the updates.

>A DataSet is completely separate from the data adapter(s) that fill it. You can use as many data adapters as neccessary to fill/update a dataset.
>
>The real trick will be creating the DataSet's schema. I suggest creating two data adapters, then generate a dataset for each adapter, then manually combine the two schemas.
>
>>I'm writing an application which uses ADO.NET in disconnected mode.
>>
>>It connects to one Visual Foxpro 8.0 database file, and one Visual Foxpro 8.0 free-standing table located in another folder.
>>
>>The OleDbDataAdapter only allows the SELECT statement to use one connected database at a time.
>>
>>Is there a way I can build a dataset which allows me to merge multiple SELECT statements into a single dataset, or from multiple oldDbDataAdapters?
>>
>>For Example:
>>SELECT * FROM dbcompany WHERE name = "IBM" INTO file1;
>>SELECT * FROM dbsubscriptions WHERE name = "IBM" INTO file2;
>>SELECT * FROM file1, file2
>>
>>I'm new in the DOT NET programming.