At 11:49 PM 12/07/2006, you wrote:

>Hi
>
>I do have problems in handling multi table forms for order and invoices.
>
>Typically the code is written to
>
>1. Save the header / master record (using a transaction)
>2. Grid / textbox control to enter transactions.
>
>I am unsure as to how to proceed with the transaction control in this
>case.

Do you understand the "master/detail" concept? If you set up the
header (master) query and the detail ("transaction") using the
inbuilt master/detail handling structures, IBO takes care of the
relationship for you. Ask further if you need an explanation of how
to set up a master/detail relationship.

As far as transaction control is concerned (assuming you are
referring to database transactions here, not "user transactions"),
all work that is part of a single task should *always* be done within
a single transaction. In fact, the various "link" relationships in
IBO will either misbehave or not work at all if you try to separate
the parts into separate transactions.

When working with IBO, don't think about "forms" as being the
taskmaster. Everything in IBO happens in the datasets: forms -
specifically, the data-aware visual controls on them - are smart
containers, providing the visual interface between the user and the
datasets. The statement classes (including, but not limited to,
datasets) have a lot of properties and methods that avoid the need to
code special behaviour into your visual control's events.

Helen