If you're using queries your problem may be:
You can't use cached updates for the detail query in master-detail
relationship where the relationship is governed by the "DataSource" setting
because the detail query is requeried every time you scroll the master
dataset.
You also have to handle deletes with referential integrity in the correct
order etc - basically cached updates are just temporary paradox tables in
the "Priv" directory.
Max
[Mark Said]
On Wed, 25 Aug 1999, Myles Penlington wrote:
> A word of advice. If you can avoid it don't use Cached updates - There
> is just too many bugs in it.
What sorts of bugs?
> Use the TClientDataset instead - I think it only comes with the C/S
version
> - Works like a dream by comparison and it is especially good for Master
> Detail updates etc.
Currently I'm using D4Pro, the only reason I'm using cached updates is so
that I can let the user edit all the data on the form, and "save changes
y/n/cancel" when they close the form. So far it all works nicely, apart
from handling this second table.
Mark
--
Mark Derricutt | Chalice of Blood
Software Developer | New Zealand Christian Music News
Auckland, New Zealand | http://www.chalice.gen.nz
[EMAIL PROTECTED] | UIN: 1934853
Getting jiggy with Mortification - Martyrs
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
