Can the above be done on the server at the same time? Effectively, I want to update a descripion in one table and then update the address, city, state and zip in another table. I am using vs.net with an access databas, oledbcommands and executereader. The tables have a one-to-many relationship.

Here is my code:

UPDATE stlocation
SET storeaddrl1 = ?, storecity = ?, storestate = ?, storezip = ?
WHERE (storeid = ?)
__________________________________________________ ______________

Notice above that I have no Description field. That's because it is in the sthdr record.

Can I do something like:

UPDATE sthdr, stlocation
SET storedesc = ? storeaddrl1 = ?, storecity = ?, storestate = ?, storezip = ?
WHERE (storeid = ?)

Or can I do something like below in the oledbcommand:

Update storehdr
Set storedesc = ?
where (storeid = ?)

UPDATE stlocation
SET storeaddrl1 = ?, storecity = ?, storestate = ?, storezip = ?
WHERE (storeid = ?)

Thanks for answers.

You can use transactions. Assign a transaction to your command objects, begin the transaction, execute all of the commands, then commit the transaction. If you dont want to persist updates that have occurred since the transaction began simply rollback the transaction.

All samples of .net stuff use single table updates. In the real world, many tables are related for processing updates. This update I am referring to is the most basic that exists. Is what you said the only way to update 2 tables when the user clicks submit? Apparently a datagrid only allows for edit/delete and canel. A adapter only deals with one table at a time. I don't see anything that works with a dataset either. The pubs database has a titles and authors relationship. Are you saying that the only way to add a new title and author is to use transaction processing?

It may not be the only way, after all, you could write a command that contains an SQL Update query that updates more than one table (i think your initial post had such a statement so you are obviously aware of this).

It is the 'Correct' (Microsoft tm)s way of doing it though. Transactions have been around for a long time and will probably be used more with the introduction of .NET.

DataAdapters are capable of handling data from multiple tables in a database, but Microsofts preferred way of doing it (at least from what I have read) is to use a different DataAdapter for each table. The real bitch about transactions used with DataAdapters is that each command (that modifies data) in a dataAdapter needs a property setting to the transaction object you are using.

Doesnt sound like what you want to hear but I hope it helps.