Re: Big Blunder, Help!
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/metacard@lists.runrev.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
Re: Big Blunder, Help!
At 11:15 PM 8/23/01 +0900, you wrote: >There is a single database file accessed by a small Macintosh ethernet LAN. The file is kept on the server's shared folder >and a few other computers access it occasionally and make changes. When it was in hypercard, if it was currently being used, >then when one of the other computers tried to access it, it got a "this file is busy" report and they could not access it >until after the other person was done. This kept things nice and kosher. However, after I converted it to Metacard, it no >longer reports this, and I get simultaneous changes from multiple computers, some of which do not get saved. This is a big >problem. Any solutions would be greatly appreciated. > Mark! 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. Good Luck Jack Rarick Braintree Athletic Systems Archives: http://www.mail-archive.com/metacard@lists.runrev.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
Big Blunder, Help!
There is a single database file accessed by a small Macintosh ethernet LAN. The file is kept on the server's shared folder and a few other computers access it occasionally and make changes. When it was in hypercard, if it was currently being used, then when one of the other computers tried to access it, it got a "this file is busy" report and they could not access it until after the other person was done. This kept things nice and kosher. However, after I converted it to Metacard, it no longer reports this, and I get simultaneous changes from multiple computers, some of which do not get saved. This is a big problem. Any solutions would be greatly appreciated. mark mitchell Japan Archives: http://www.mail-archive.com/metacard@lists.runrev.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
