Problem saving detail in mstr/dtl application.
From: Debbie Erickson (knmc_at_montereypark.ca.gov)
Date: 03/22/04
- Next message: Júlio Silva: "Re: CheckMod.db"
- Previous message: Max Odendahl: "Open Tab delimited file with ADO"
- Next in thread: Del Murray: "Re: Problem saving detail in mstr/dtl application."
- Reply: Del Murray: "Re: Problem saving detail in mstr/dtl application."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 22 Mar 2004 09:42:08 -0800
If I edit my master record, then edit the detail, both will save correctly.
But if I try to modify the detail without changing the master, my screen
controls "appear" to be correct, but the actual data never gets written out
to the database.
A bit of background: I use adodatasets, where I link the detail to the
mastersource. I also have client datasets and a dataset provider. The
datasetfield is set on the detailCD. In the beforeedit, before insert,
before delete events of the detailcd, I check the status of the mastercd.
If it is in browse mode, I force the mastercd into edit status. I do the
applyupdates within a transaction block. As I trace the program, it looks
like it follows the same logic path when I save a record, whether the master
contained changed data or not.
I have one master with several fields on the screen, and one dbgrid to allow
entry of the detail. When I add or delete a detail record, the grid looks
like the detail was added/removed.
What are some common mistakes that may cause the detail not to update
correctly? I see another poster, Joao Kho with a similiar question. Except
he's using the batch approach whereas I am using the transactional method.
- Next message: Júlio Silva: "Re: CheckMod.db"
- Previous message: Max Odendahl: "Open Tab delimited file with ADO"
- Next in thread: Del Murray: "Re: Problem saving detail in mstr/dtl application."
- Reply: Del Murray: "Re: Problem saving detail in mstr/dtl application."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|