I have found an interesting problem when using transactions.
Works like this
use view1
use view2
set both to table buffering
begin transaction
insert into view1

begin trans
insert into view2
end trans
begin trans
insert into view2
end trans
begin trans
insert into view2
end trans

end trans

if you look at view2 you will see that 1 or more records are currupted. Append blank has the same behaviour.
I know there is no tableupdate etc but for my situation with tablebuffering I don't want to issue till the user saves (i have a screen with fields from many tables both parent and child) have constructed a container object for the child table this is where the 2 transaction is used. Any body got ideas.