dbTalk Databases Forums  

Record lock

comp.databases.filemaker comp.databases.filemaker


Discuss Record lock in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
eyebrown@mindspring.com
 
Posts: n/a

Default Record lock - 12-03-2005 , 07:37 AM






I'm running FM 6 in a served environment with about a dozen users.

There are circumstances where I need to update a found set in a file while
it is being used. As my replace-with-calc cranks through, when it hits a
record a user is viewing I get the "cannot modify because so & so is
using". I click "continue", and it presumably continues, leaving that one
record unupdated.

Somewhere I ran across a technique for trapping this error, storing the
record's key field in a global or something, then letting the script
progress. After, the script would rerun for just that record, assuming it
has been freed up by then.

Can anyone give me pointers for example templates and/or URLs for past
threads on this topic?

Steve Brown

Reply With Quote
  #2  
Old   
Paul Bruneau
 
Posts: n/a

Default Re: Record lock - 12-05-2005 , 01:26 PM






eyebrown (AT) mindspring (DOT) com wrote:
Quote:
I'm running FM 6 in a served environment with about a dozen users.

There are circumstances where I need to update a found set in a file while
it is being used. As my replace-with-calc cranks through, when it hits a
record a user is viewing I get the "cannot modify because so & so is
using". I click "continue", and it presumably continues, leaving that one
record unupdated.

Somewhere I ran across a technique for trapping this error, storing the
record's key field in a global or something, then letting the script
progress. After, the script would rerun for just that record, assuming it
has been freed up by then.

Can anyone give me pointers for example templates and/or URLs for past
threads on this topic?
I think you'll have to let go of Replace and go to a loop instead, at
least that's what I did.

You turn on error trapping. There is an error code specifically for
"record is busy" that you can check for. As you go through the loop,
you can build up a multiline key of any un-updated records in a global
and then when the loop is over, use "Go To Related Records (show)"
using a self-join relationship to make a set of those un-updated
records.

Then you have to figure out what to do at that point, because as we all
know, sometimes records can be busy for a long, long, long time.



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.