|
Home > Archive > Programming with dBASE > July 2005 > Retry lock cancel
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| When an automatic lock is attempted, the message ?Row is in use by another, Retrying lock?? appears if another user is editing the record. The cancel button on this message I thought would stop any attempt to lock and return the user to their original sc
reen.
But clicking cancel does not stop the lock attempt. I am familiar with _app.databases.current.session.lockretrycount , but I believe that only sets the number of attempts before the user sees the ?Row in use? message.
Since Cancel is the only option on the Row in use? screen, you can hold down the enter key and eventually (maybe 100 cancel attempts) the user is put back to the screen and can move to another record. But how can I get the cancel button to really cancel
any further attempt to lock the record once the user has been notified the record is locked by another user?
Am using 2.21 on XP
Thanks for your help on this,
Rick
| |
| Bob Buchanan 2005-07-27, 8:23 pm |
| Hello Rick:
When the lock is valid in my app, the user only needs to click the button
twice to cancel the lock attempt. If more than that, there is another
occurrence of the table that is active somewhere. If the lock is valid when
two users attempt to edit the same customer, the late arrival gets the
message and can cancel in two clicks. They are then returned to the edit
screen -- and must cancel from the editor itself - but edit keystrokes are
dead.
I decided to use my own dialog for some situations. Look at the "override In
Use message" thread here dated 6/20. It may help.
Regards, Bob
Robert Buchanan
RLB & Associates
(916) 761-8737
www.rvspacemanager.com
"Rick" <Sportman7@netzero.net> wrote in message
news:ww3OIRtkFHA.1756@news-server...
> When an automatic lock is attempted, the message ?Row is in use by
> another, Retrying lock?? appears if another user is editing the record.
> The cancel button on this message I thought would stop any attempt to lock
> and return the user to their original screen.
>
> But clicking cancel does not stop the lock attempt. I am familiar with
> _app.databases.current.session.lockretrycount , but I believe that only
> sets the number of attempts before the user sees the ?Row in use? message.
>
> Since Cancel is the only option on the Row in use? screen, you can hold
> down the enter key and eventually (maybe 100 cancel attempts) the user is
> put back to the screen and can move to another record. But how can I get
> the cancel button to really cancel any further attempt to lock the record
> once the user has been notified the record is locked by another user?
>
> Am using 2.21 on XP
>
> Thanks for your help on this,
> Rick
>
| |
|
| Hi Bob,
I am testing out the network capability of an app, and am finding some problems. I use autoedit so most recordlocking is not explicit. I do some fancy things with some form controls that when changed update more than one rowset where I do explicit locki
ng to be sure all rowsets are locked, updated, then unlocked together.
I think I just need to do some more legwork, testing more of those locks. But do have one important question. I figured that the onchange code of a combobox would not run if the lock fails, but it seems to run even after a failed lock. The combobox is
datalinked to a field in the rowset.
Do I have that right -- the controls onchange code continues even if the datalinked control produced a failed lock? If so, I must need to place a lockrow check in each combobox onchange code to prevent that code from running.
Thanks,
Rick
Bob Buchanan Wrote:
> Hello Rick:
>
> When the lock is valid in my app, the user only needs to click the button
> twice to cancel the lock attempt. If more than that, there is another
> occurrence of the table that is active somewhere. If the lock is valid when
> two users attempt to edit the same customer, the late arrival gets the
> message and can cancel in two clicks. They are then returned to the edit
> screen -- and must cancel from the editor itself - but edit keystrokes are
> dead.
>
> I decided to use my own dialog for some situations. Look at the "override In
> Use message" thread here dated 6/20. It may help.
>
> Regards, Bob
>
> Robert Buchanan
> RLB & Associates
> (916) 761-8737
> www.rvspacemanager.com
>
>
>
> "Rick" <Sportman7@netzero.net> wrote in message
> news:ww3OIRtkFHA.1756@news-server...
>
>
|
|
|
|
|