Subject | Locate & Lock Conflict |
---|---|
Author | Robert F. Tulloch |
Post date | 2001-02-09T04:43:06Z |
Hi:
I was testing App (BCB5 sp1-IB6-IBX 4.42) and had some problems in code with
Bookmarks (freeing NULL). I test several times and kept crashing the app.
I fixed that an a while later I did a locate on the same table and got IB error-Lock
Conflict. I tried to validate (from my app) and it just hung. I then went to IBConsole
and noted that I was logged on as SYSDBA 6 time! I thought when the app crashed and I
reset it, it would drop the logged on user. O well.
After shutting down and restarting IB server, all the extraneous logons were gone
and my Locate() worked again with no problems.
I don't understand why a record lock conflict would arise from a Locate() and does
this mean one should wrap all locates in a try-catch?
Thanks for any help/info.
Best regards
I was testing App (BCB5 sp1-IB6-IBX 4.42) and had some problems in code with
Bookmarks (freeing NULL). I test several times and kept crashing the app.
I fixed that an a while later I did a locate on the same table and got IB error-Lock
Conflict. I tried to validate (from my app) and it just hung. I then went to IBConsole
and noted that I was logged on as SYSDBA 6 time! I thought when the app crashed and I
reset it, it would drop the logged on user. O well.
After shutting down and restarting IB server, all the extraneous logons were gone
and my Locate() worked again with no problems.
I don't understand why a record lock conflict would arise from a Locate() and does
this mean one should wrap all locates in a try-catch?
Thanks for any help/info.
Best regards