Look at a artilcle at undu.com. (Great site btw...) There is a few article's
how to load an 'privat' datatamodule for every childwindow.
http://www.undu.com/Articles/981229d.html. I think this wil do the trick.
I'am just starting a project where a want to do the same as you.

Bram van der Voet


-----Oorspronkelijk bericht-----
Van: Chris Landowski [mailto:chrisl@...]
Verzonden: woensdag 10 januari 2001 09:06
Aan: ibobjects@egroups.com
Onderwerp: [IBO] Proper Transaction Usage in an MDI App


In an MDI style app, is it typical to use a separate transaction on each
child form with an isolation of tiCommitted ?

I have tried using a single transaction on a shared datamodule but when I go
to post my changes, datasets on other child forms that are in an edit state
automatically post.

Could someone please advise me on the best method for transaction handling
in and MDI style app. I would like the changes made in one child form
visible to the remaining child forms as soon as they are posted, but do not
want datasets on other child forms affected. I would also prefer to keep the
transactions as short as possible. Is the default transaction even an option
for me ?

Thanks in advance,

Chris Landowski
Dynamic Software Solutions