At 01:14 PM 25/09/2004 +0000, you wrote:

>Hi,
>
>I'm extending an old application developed using IBO 3.6d.
>When inserting a new record into a joined-query with an
>attached "InsertSQL" property/statement - using a TIB_Grid - the
>first two fields are inserted (using lookup combos) without any
>problems, while the last field - a decimal - becomes read-only in
>the grid.
>
>I've tried setting a value on the underlying field on the "After
>Insert" event. That works fine and the value is displayed correctly
>in the grid - but still cannot be edited.
>
>When editing a record in the grid (using the "EditSQL" statement),
>the field can be edited without any problems.
>The generated "InsertSQL" statement is as follows:
>
>INSERT INTO TSA_M_UNIT_COST(
> COSTTYPE, /*PK*/
> COUNTRYCODE, /*PK*/
> TIMEUNITCOST)
>VALUES (
> :COSTTYPE,
> :COUNTRYCODE,
> :TIMEUNITCOST)
>
>The problematic field - TIMEUNITCOST - is *not* declared read-only.

Is it possibly a computed field of some kind? Could you check its
ColumnAttributes and also show the SQL for the dataset?

Otherwise...IBO 3.6 is so incredibly old, I wouldn't have a clue by now
whether there was a bug affecting this.

Helen