Okay, so I figured out what was happening -- and this is weird! The Windows 2000 machine in question lives on a network. On this network is a server that houses the organization's files. The Win2k box in question was opening Ebase, but not from cached copies, nor from local copies as I and others had suspected, but was instead being very precocious in that it was loading Ebase from a backup stored on the network drive! By manually redirecting Filemaker to look on the local drive, and _then_ hitting the hosts button, we can open Ebase correctly from the machine that's serving it. But every time we restart Filemaker, it's back to looking at the backup. Now the obvious solution is to remove the back/do the backup elsewhere, but i'm reluctant to do that, as that to some degree defeats the idea of having a server that's backed up. So, if anyone has any ideas on how to have this organization continue to use their network as a place to park files till they're backed up onto some other media while also keeping this one Win2k machine from trying to open the backups, I'd love to hear them. thanks, -arif -- Arif Mamdani Circuit Rider LINC Project -- Welfare Law Center www.lincproject.org www.welfarelaw.org p: 212.633.6967 ------------------ 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 ---------------------------------------------------------------------
