I figured that was the problem. I thought maybe I could ADD the tables to the DBF, do the Transaction stuff, then REMOVE them. I tried issuing "ADD TABLE c:\blah\blah\blah.dbf" commands through the OleDbCommand object in ADO.NET, but I just get an exception "One or more errors have occurred processing the command.". So maybe the VFP8 OleDb driver doesn't support ADD TABLE or REMOVE TABLE.

The solution I ended up using was when the Transaction begins, make backup copies of the DBFs. If the Transaction is rolled back, restore the DBFs from the backups. If the Transaction is committed, delete the backups. It works. I have multiple INSERTS and UPDATES to SQL Server tables and VFP free tables, and if anything goes wrong I can rollback the changes to both now with no problem.

-----
Lee Perkins

>Transactions are not supported on free tables.
>
>
>>Does the VFP8 OleDb Driver support transactions? I'm doing UPDATEs and INSERTs against several free DBFs in VB.NET using the VFP8 OleDb driver. I'm using a System.Data.OleDb.OleDbTransaction object to wrap several UPDATEs and INSERTS in a transaction. If I roll the transaction back in the middle, the UPDATEs and INSERTS done so far are actually comitted. They don't get rolled back.
>>
>>Could I be doing something wrong, or does the VFP8 OleDb Driver just not support transactions (or at least not for free DBFs)?
>>
>>-----
>>Lee Perkins