At 02:46 PM 7/20/2004 -0400, you wrote:
I reported the problem to RBASE tech support but so far, no answer from
them on this issue.
Mark
Mark,
We have spent time on this over the phone with your database and other
sample databases and were unable to duplicate the table lock.
Based on the previous threads, we may have a growing issue and would
appreciate any additional feedback from yourself and any other users. It
appears the problem may be stemming from exiting a form incorrectly
and R:BASE is keeping the lock on the table. One item to check is if
there is a .$$$ file hanging in the scratch directory with the same date
and time stamp as when the incorrect form exit occurred.
John
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence
Lustig
Sent: Tuesday, July 20, 2004 2:43 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - RE: Extra table locks
> I have experienced the same problem, just yesterday.
> It looks like the
> only thing that you can do is to disconnect all
> users from the database.
> I am still waiting for anybody to tell me how to
> unlock the table
> without having to disconnect all users from
> database.
Bad news. The client I'm at is a 24/7 operation --
they never get all users out of the database except
for maintenance, even that isn't regularly scheduled.
Have you reported this, and do you have a reproducible
case using ConComp or another of the sample databases?
--
Larry
John Minyo II
R:BASE Technologies, Inc.
Customer Service
[EMAIL PROTECTED]
www.rbase.com
(724) 733-0053
