> 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.
> 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

This sounds to me like you've gotten something looked up incorrectly
(the wrong datasource or keysource or something). Perhaps if you post
the relevant parts of the DFM (not as an attachment, just cut-n-paste
from the view form as text option) we may be able to provide more
specific help.

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

The whole point of a transaction is to create a common context for
your changes, which ever table the changes come from. There are two
aspects to this common context...

1. All tables can see the data from all other tables in the same
transaction (whether the changes have been commited or not). You may
need to refresh or use the IBOs DMLCache mechanism to see the changes
at the client, but they are visible to each other at the server.

2. Changes to all tables using the same transaction will be all
committed or all rolled back (you get wont get the situation you see
in traditional desktop systems where only half the changes have been
saved).


So if you want the above situation (which is the common situation for
all items on the one form) then you will want to use just one
transaction. Only if you want to protect one view/changes of data
from another will you want separate transactions (as is often the case
between different forms).


I suggest you work through some of the IBO tutorials. For more
general transaction info you may also want to take a look the
documentation link on this site: http://www.cvalde.com/


HTH

Geoff Worboys
Telesis Computing