Thanks for your rapid response.
I've rechecked the query - and the column is not computed, set to
read-only or similar.

The underlying query is pretty straightforward:

select b.countrydesc,
a.costtype,
a.countrycode,
a.timeunitcost,
c.costtypename
from tsa_m_unit_cost a, cm_country b, tsa_m_cost_type c
where a.countrycode = b.countrycode and
a.costtype = c.costtype
order by b.countrydesc, c.costtype

Best regards and thanks

Michael

--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> 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