Re: Locking Tables Via SQL*Plus, ODBC - IGNORE

Please ignore. Turns out it was programming error. Turns out that the MFC statement that locked the table was deallocated, which in turn rolled back the lock.

Sorry,
David

In article <7fim6t$b8o$1_at_nnrp1.dejanews.com>,   dgriffiths_at_my-dejanews.com wrote:
> We're having a strange problem with locking tables in back-end applications.
>
> We have to instances of the application that "share" the data for processing.
> In order to guarantee consistancy, one instance will lock the table, process
> the data, and then unlock the table.
>
> It didn't seem to be working in ODBC if the applications log onto the database
> with the same userid and password. If instance A locks the table, and then
> instance B locks the table (while instance A still has it locked, and without
> the NOWAIT option), it gets locked by B as well. Basically, B can update the
> table while A has it locked.
>
> SQL*Plus doesn't allow this to happen. If A has it locked, B will block until
> A releases the lock.
>
> Anyone have any ideas?
>
> Thanks,
> David
> GTE Enterprise Solutions
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Tue Apr 20 1999 - 16:01:03 CDT