Of Charles Barouch
Sent: Saturday, May 27, 2006 3:36 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Locking Error (Maybe SB+, maybe UV)
Mark,
That appears to work. I'm really not sure why, though. I appreciate
the help.
--
Charles Barouch
[EMAIL PROTECTED] - Consulting
[EMAIL PROTECTED
]
Date: 27/05/2006 01:46
Subject: [U2] Locking Error (Maybe SB+, maybe UV)
I'm getting this error and I don't know how to fix it. A full reboot
hasn't helped:
Program UPDATE.OI.GL.FROM.ORDER:
Line 97, FATAL: The locks necessary for database operations at the
current
I'm getting this error and I don't know how to fix it. A full reboot
hasn't helped:
Program UPDATE.OI.GL.FROM.ORDER:
Line 97, FATAL: The locks necessary for database operations at the current
isolation level (0) are not held by this process.
The program
is a basic subroutine which is called by
If your Trigger Subroutine is going to Write, it must be first READU the
item.
Mark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Charles Barouch
Sent: Friday, May 26, 2006 8:47 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Locking Error (Maybe SB
Not too familiar with sb, but if it is re-opening the file, then any
record locks are lost. A workaround MIGHT be to issue a RECORDLOCKU in
the subroutine prior to the write.
j
On 5/26/06, Charles Barouch [EMAIL PROTECTED] wrote:
I'm getting this error and I don't know how to fix it. A full
Mark,
That appears to work. I'm really not
sure why, though. I appreciate the help.
--
Charles Barouch
[EMAIL PROTECTED] - Consulting
[EMAIL PROTECTED] -
ETL/Migration/Integration
(718) 762-3884x1
Mark Eastwood
wrote:
| If your Trigger Subroutine is going to Write, it must be
first READU
