Xref: utzoo comp.sys.mac:49855 comp.sys.mac.programmer:12887
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer
Subject: Re: Problems with Multiuser Foxbase+/Mac
Message-ID: <10581@hoptoad.uucp>
Date: 5 Mar 90 00:51:01 GMT
References: <940@uvicctr.UVic.CA.UUCP>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 24

In article <940@uvicctr.UVic.CA.UUCP> cwoytow@uvicctr.UUCP (Colin Woytowich)
writes:
>I am having a problem with the Multiuser capabilities of FoxBase+/Mac.
>My database runs fine on a single machine or with read only operations
>from multiple users.  However, the first user into a database has full
>read/write capabilities (regardless of which user it is) while all
>subsequent users accessing the db are restricted to read only access
>(error message "cannot write to read only file").  Tops seems to be
>working fine as the users can copy files to/from remote volumes
>(published as Many Writers; mounted as Read/Write, HFS).
>        Network: MacPluses & SE30 with LocalTalk and Tops (V2.0)

FoxBase+/Mac had some problems with earlier versions of TOPS because of
the FoxBase developers' reliance on Appleshare-specific behavior of the
PBLockRange command.  I'm not sure, but what you're observing is
probably someone's workaround to prevent the problem from happening.
TOPS 3.0, available now, has made its PBLockRange command work exactly
like Appleshare's, and it claims to have solved all problems that
multiuser databases had with it.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"Conversion, fastidious Goddess, loves blood better than brick, and feasts
 most subtly on the human will." - Virginia Woolf, "Mrs. Dalloway"