Re: "Field cannot be updated" error with ADODataSet

From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 06/30/04 

Date: Tue, 29 Jun 2004 22:48:30 -0500

>1. Is it theoretically okay, that the master dataset has pessimistic
>locking and the detail dataset has optimistic locking?
When I run a quick test using ltPesamistic, serverside cursors and TableDirect I
can edit a table but in general Ado doesn't work well with pessimistic locking
so I don't recommend it.

>
>2. Will it (the above) suit my scenario, with three connections... when I
>tested it initially, there was a huge performance loss.. after
>modifying and posting a record on one computer, the other
>computer would hang when attempting to browse the DBGrid,
>as if the processor was at 100% utilization or something..
>Any optimum suggestions in this regard?
I don't know what the "above scenario" is actually referring to?
But TableDirect mode is generally the fastest way to connect to an Access Table.
I would recommend you stick with optimistic locking. 

--
Brian Bushay (TeamB)
Bbushay@NMPLS.com