Hi, all !

I have this huge problem with a rewritten application. I'll try to
explain
what's happening and what's done inside the application:

1. Logging on to server
2. Checking table USER_SETTINGS to check it's a valid user, and if
found
valid:
2.b) Load user settings.
2.c) Write Logindata (machine, 'Now') to this record in an UPDATE
statement.
3. Close transaction
4. Open TIBODataSet in a grid (only first XXX rows are shown. A
ReadOnly
dataset.
5. (User uses application)
6. When application is closing, LoginData is written, now with NULL
for all
values written upon startup.

The error:
When I start 2 instances of this application with the same user name,
I get
the "deadlock" error when closing app nr. 2. No matter if it was
started
first or last. I am fairly sure all writings to table USER_SETTINGS is
committed immediately.
I know the problem is within writing the last table, because the error
doesn't appear if I write to another record here.

Questions:
- How can this happen ?
- Is there a way I can *not* have the Commit; actually _commit_ when
called
explicitly ?

I'm at a complete loss here.

Thanks in advance !


--
Regards,

Bjørge Sæther
bjorge@haha_itte.no