At 11:15 AM -0600 7/18/02, Eric Johnson wrote: >Andrew, > >Another approach is to set files to multi-user and have a copy of FMPro >running ebase on a host machine. Other users will also have to have a copy >of FMPro and use FM's networking features to access the data on the host >machine. This is fairly similar to having FMServer, but will not support as >many users and is not very robust. You are quite a bit more likely to have >problems with file corruption, etc., under this scenario, if I understand >correctly. I do _not_ recommend this approach. Data's priceless, and >recovering from disaster is very expensive and/or time consuming.
In my experience, this is not a viable option. When we tried to do this with two users, the database would crash every time both users tried to access the same record (a frequent occurence, actually, even with two users -- one hollers, "hey, do you remember karen charney?" the other opens karen's record, and crash). When the database crashes, it frequently corrupts the files. Because Filemaker's "Recover" facility is seductive but untrustworthy, this is a scenario for disaster. Use FMP Server for multi-user access, don't allow any end user applications on the computer running FMP Server, and protect it with an ininterruptible power supply and regular backups. Cheryl Chase Mathias Consulting http://www.mathiasconsulting.com ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
