>Does anyone have an informed understanding of just what FMPro is doing in >this or similar situations?
I've never tried to test for the exact details, but basically FM stores related file info as a filename and a directory path. If either changes (ie. you move a file, rename a file, or both), you get the "can't locate file" dialog. Trouble is, FM stores related file info once for each instance of relatedness - once for each relationship, once for each external script call. It's not hard to get some of those file references pointing to one copy and some to another, such that a single file is working with two or more copies of a related file.... and it can be difficult or impossible to detect this situation before a mess is made. Compress copies of ebase you're not using; FM can't open or interact with a compressed database, and the archive guarantees that you'll always have a backup. -Allen -- L. Allen Poole ebase user support Creative Database Solutions NW 3640 SE 26th Ave. Portland, OR 97202 [EMAIL PROTECTED] (503) 720-3742 ------------------ 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 ---------------------------------------------------------------------
