At 11:14 AM -0400 8/23/01, Jack Rarick wrote:
>My easiest solution is to use a text file as a flag. When your client app
>starts up it first checks to see if the text file (which resides on your
>server's shared folder) contains the words "In Use" - or "Whoa" or
>something. If it does, the app eithers waits a short time or gives the user
>a choice before trying again.
>
>If the text file reads "Go!" then immediately continue starting your client
>app and write "In Use" to your text file. Do your DB work and when
>quitting, write "Go!" to the text file.
>
>This works for me in a cross platfrom environment as well.
For an informal setup, this is exactly what I would have suggested. There are obvious
issues with such a system (one being: what happens if someone opens the file and loses
their connection?) but setting those aside for the moment, couldn't this also be
implemented within the stack itself? The opening script would contain something like:
if the inUse of this stack then
quit
else
set the inUse of this stack to true
save this stack
end if
Then continue editing the stack. When saving at the end, do something like:
set the inUse of this stack to false
save this stack
quit
regards,
Geoff
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
