COSTAS,

> I have a form with two TIB_QUERY objects,two IB_DATASOURCES and two
> IB_TRANSACTIONS and also one connection.One query is for the PROJECT
> table and the other for the PROJECTTYPE table.I also attach to each
> two TIB_TRANSACTION .The field 'TYPE' in the PROJECT table is looked
> from the PROJECTTYPE table.I have set up a TIB_LOOKUPCOMBO as
> described in the GETTING STARTED GUIDE FOR IBOJECTS.Everything is
> working fine as far as the TIB_LOOKUPCOMBO box is concerned but
> i have noticed the following strange behavior,i am sure i am doing
> something wrong because i am new to IBOBJECTS and client/server.
> a.When I scroll the PROJECTTYPE TABLE using a TIB_GRID i have noticed
> that sometimes a record is inserted in the PROJECT table and the
> table gets into edit mode.

I would like to see the callstack on those unexpected changes into edit
modes. Perhaps there is something I can do to help or perhaps we can spot
what you are doing in your code to bring those states on.

> b. The value of the 'TYPE' field of the current record in the
> PROJECT table changes value to correspond to the current record
> of the PROJECTTYPES table current record and gets into edit mode

I don't recommend you use the word TYPE for a column name. That is a
reserved token.

> Please help me to understand what I am doing wrong.Also please tell me
> if its a good policy to use a separate transaction TIB_TRANSACTION
> for each table.

I don't think you need a separate transaction for each of these tables.
It really boils down to what you want to take place update-wise as a single
unit of work.

The way you have it there wouldn't allow you to make changes in both tables
and commit or rollback the changes as a single unit of work. Things have to
be in the same transaction context to be in a single unit of work.

> Again I apologies for the CAPS.

We forgive you!

Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com