Subject | for every form a different transaction object ? |
---|---|
Author | L.M. Bemmelmans |
Post date | 2003-07-22T08:44:38Z |
Hi,
The "pessimistic" lock option of IBobjects works great....as long as you do
not COMMIT or COMMITRETAINING. Sounds obvious, but what if one application
can have more than 10 forms open at the same time ? Each form is a unit of
work. For instance: invoice-form, customer-form.
I would like to post changes to the database at once, so basically I commit
after every post. But if I do so on form10 my recordlocking on form1
disappears.
So I'm thinking of putting a transaction component on each form ( actually
on the datamodule belonging to that specific form )
Is this good practise ? It means that one application could have 15 active
transactions (15 forms open, all in editmode)
Leon
The "pessimistic" lock option of IBobjects works great....as long as you do
not COMMIT or COMMITRETAINING. Sounds obvious, but what if one application
can have more than 10 forms open at the same time ? Each form is a unit of
work. For instance: invoice-form, customer-form.
I would like to post changes to the database at once, so basically I commit
after every post. But if I do so on form10 my recordlocking on form1
disappears.
So I'm thinking of putting a transaction component on each form ( actually
on the datamodule belonging to that specific form )
Is this good practise ? It means that one application could have 15 active
transactions (15 forms open, all in editmode)
Leon