>as it turned out, the host machine was simply not opening all the necessary >files in the ebase suite. > >know of a quick and easy way to do this, beside opening up the "define >relationships" function in the "names" file?
Another method is to create a new FileMaker file with a script that opens ebase.103, and all the ebase files that the standard routine doesn't open. An additional benefit of this is that you can add other FileMaker files to the script that you want to open routinely, such as an event registration file or the like. Set the Document preferences on this file to run your "openall" script on startup, then use this file like an alias to launch ebase. -- -- 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 ---------------------------------------------------------------------
