> Hi all,
> I have an Access (2003) frontend db using Oracle backend (10gR2). I
[quoted text clipped - 28 lines]
> Does anybody have success in locking an Oracle record to prevent
> another user from making changes to it? Thanks.
Could it be that the event fires and issues a commit? In which case
the lock would not hold. How can one leave a transaction open?
Bob Hairgrove - 03 May 2007 19:59 GMT
>> Hi all,
>> I have an Access (2003) frontend db using Oracle backend (10gR2). I
[quoted text clipped - 31 lines]
>Could it be that the event fires and issues a commit? In which case
>the lock would not hold. How can one leave a transaction open?
You need to turn auto-commit off in the ODBC properties dialog. Also, check the
documentation for "transaction isolation" in the ODBC docs -- I believe you want
"serializable". This needs to be set in the same ODBC setup dialog for your
Oracle connection. By default, Access (and Oracle, I believe) use "read
committed" ... but it has been awhile since I worked with Oracle and ODBC.
If all else fails, you can do an ODBC trace to see whether these options are
actually kicking in.
--
Bob Hairgrove
NoSpamPlease@Home.com