> OK, so are you saying that the main dataset is retrieving

information from the lookup dataset, other than the text associated
with the lookup key?

No. Retrieved information is the Primary Key of the Lookup table.
I want a dropdown list to appear when the user enters the appropriate
column of the grid. On selection the main detail table will contain
the selected field i.e. the primary field of the lookup table.

This works before I Cut & Paste the LookupCombo control into the grid.
I have an update bar linked to the main details datasource. The user
can append a new record with the update bar. The grid correctly shows
a new, blank record. If the user(with the lookupcombo placed outside
the grid) enters the lookupcombo, selects a record from the presented
list, the grid correctly shows the selected field from the lookup
table. This also works if the user edits a currently selected
existing record.i.e if the user enters the lookupcombo and selects a
different record in the lookup table, the data in the main detail
table changes.

If I then Cut & Paste the LookupCombo, then at run time, the control
is not shown when I enter the appropriate column of the grid. This is
why I was wondering if I need to take more control of the transaction
rather than relying on the update bar to handle transaction control.

>
> Are you saying that you have more than one keylinks pair defined

between the lookup dataset and the main dataset? (This MATTERS.)

>

No , only 1 pair.

Doesnt the fact that I have the process working correctly if the
Lookupcombo is outside the grid indicate that links and properties
have been set correctly ?

Mike