Cached updates, tClientDataSets - that's OK, thank you for the suggestion
and the nice URL.

BUT, still, that doesn't solve one problem: if I have a local copy of the
data I'm editing, I can not run a query against it. What am I going to do
about that?! If there are just simple sums, it's OK, but mine usually are
grouped by currency and the sum is multi line. It works very well with a
query, but I'll have to write it manually I guess.

Any solutions? It sounds funny that one can not have a summarizing query
whenever there's a master/detail table involved. At least not before the
final POST, which doesn't do much good.

Thank you,
Best regards,
Dimitar Selensky

----- Original Message -----
From: "Sindu" <sindu@...>
To: "IB Yahoo" <ib-support@yahoogroups.com>
Cc: "Delphi DB" <delphi-db@...>
Sent: Wednesday, March 07, 2001 4:42 AM
Subject: Re: [ib-support] Master/Detail - Interbase


> Hi Dimitar,
>
> I'd suggest that you use TClientDataSet as a replacement for cached
> updates. Using TClientDataSet has many advantages. Transaction life is
> very short (only when required) and you have all flexibility of a
> TDataSet.
>
> Take a look at this URL below:
> http://www.inprise.com/midas/papers/clientdataset/
>
> regards,
> Sindu
>
> On Wed, 7 Mar 2001, Dimitar Selensky wrote:
>
> > Hello all,
> >
> > This is a very old question. In many of my forms I have tables linked in
> > master/detail relation ship. When someone creates a new master record
and
> > several detail records, if the user cancels the master records, the
detail
> > records will fall in the eternity...
> >
> > One way is to use cached updates. But with cached updates I can't have a
> > query, doing a sum over some of the values (the sum is pretty
complicated
> > and needs to have a group by clause, as for example it might sum prices
in
> > different currencies).
> >
> > Another way is to use transactions. When I start inserting or updating
> > detail rows, I start a transaction and it's being commited if the master
is
> > saved and rollback-ed if it's canceled. It works perfectly, but:
> >
> > 1. The transaction life could be *very* long.
> > 2. If there's another master/detail form of the same type opened at the
same
> > time, there's a problem, as there's only one transaction (using
tDatabase).
> >
> > Is there another way of doing it? Somebody out there must have figured a
> > nicer way. I haven't found a way to have nested transactions in
Interbase.
> > Is it possible?
> >
> >
> > To unsubscribe from this group, send an email to:
> > ib-support-unsubscribe@egroups.com
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> >
> >
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>