My insight into this is purely empirical. I have never had a problem with a file that crashed and reported a sucessful consistency check. Don't know anything about the mechanics of what FileMaker is reporting in this case, but it seems to be a good result.
I'm wondering if anyone has knowledge of how accurate the Filemaker > consistency check is. That is, when Filemaker runs a consistency check > after a crash and finds no problems, is there reasonably strong > assurance that the database is not corrupted? Or is it a better > practice to always restore from a backup whenever there is a crash? > > Care to share your approach to this? > > Thanks, > Carl > -- > Carl Paulsen > New Hampshire Rivers Council > 54 Portsmouth Street > Concord, NH 03301 > 603-228-6472 > 603-228-0423 Fax > [EMAIL PROTECTED] > > ------------------ > 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 > --------------------------------------------------------------------- > > 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 ---------------------------------------------------------------------
