>We have two mac users who will need access to our ebase data. We have 1 >licensed copy of filemaker pro. I've read the archives regarding sharing >ebase. I need a head-check regarding what will be required for us to >-successfully share our ebase database across an apple talk network. One note about the appletalk network. Appletalk will work on at least two network configurations. Insure that the correct network extension is installed in the folder FileMaker Extensions (located in same folder as the FileMaker application) and that the network specification in the FileMaker preferences is set to match your network, localtalk, or (more likely) TCP/IP for Ethernet. The network extension is installed when you install the application. If it's not present, run the FileMaker installer cd again, choose Custom Installation, and select only the network software option. >Assumption #1 -- We will need to set ebase to "Multi-User" thru the Admin >screen. There was some discussion in the archives about whether or not >*all* the ebase files would be set to share or whether only currently open >files would be set to share. So, what is the correct method to allow >*safe* sharing? Other folks mentioned they had to modify their opening >scripts to execute an "open all" command vs. an "open" command. Is this >necessary? All the files need to be set to multi-user for remote users to have the full function of ebase. The button on the Admin screen calls a script that opens all the files and sets them to multi-user, so that's all you need to do. Ebase files need to be open on the "host" machine for the remote user to access them. When ebase first opens, it launches only about 10 files that are immediately needed. If the remote user were to attempt a function that required one of the files not yet open, it would give the dreaded dialog box, "File (something) is needed to complete this action and could not be found." So, people have added steps to the open script to launch all the files. There are several ways to address this. - Add steps to the script 806 - Open, which is run when the names_.10x file opens - Create a new "Open Ebase" file which contains no records, but a script that opens ebase (which opens the normal 10 files) then the rest of the files. - Manually run the "Set Multi-user" script every morning when you first launch ebase. As a byproduct, this script opens all the files. This is easiest since it doesn't require any knowledge of FileMaker, but you've got to remember to do it. >Assumption #2 -- If we only have 1 licensed copy of FMPro, we can only >access ebase from 1 machine at any given time. So, if the server has >FMPro open... no one else will be able to open it. That's correct. >From the admin manual, >it appears that we cannot simply use the run-time ebase application if we >are going to share it... we must use FMPro to open the db. Correct? Also correct. -- -- Dave Shaw H4 Consulting tel: 206-954-7526 fax: 206-625-1338 ------------------ 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 ---------------------------------------------------------------------
