>> I ran into this a long time ago and never found a solution except
>> not to use isql. I have no idea what is causing this.  As you say,
>> sticking entirely to the java drivers seems to work ok.  I think
>> closing isql may also make the changes visible??

r> I also had such a problem and never solved it either (I was using
r> InterClient). Maybe you can try different transaction isolation level?

That was the first thing... :( Maybe this hang-up issue can help to
find it out...

daniel