>We had a system crash (probably due to a power outage longer than the UPS >could handle) of the machine running FM Server, which hosts our ebase. I >discovered this some time after the fact. > >I'm wondering what the likelihood of corrupt data is ... to the best of my >understanding, if nobody was using ebase at the time, and therefore there >couldn't have been outstanding changes to be written to disk, chances are >that FM server had flushed the cache to disk (it's set to do so every few >minutes) and the data should be fine. > >Does this make sense? I'm fairly new at FM Server.
Usual disclaimers apply... But it sounds to me that if you are reading the situation right, and if FileMaker is not objecting to opening any of the files that you got away with that one. I would dig out the supporting paperwork for the last few transactions entered and check that everything got posted. -- -- 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 ---------------------------------------------------------------------
