Walt, It's really ironic that, having had a FileMaker crash this morning, I was in the process of reinstalling the application when I read your message that this can't happen. Sorry to disagree.
Something appears to hammer FileMaker itself, even when I'm not installing other software. In this instance, reinstalling the app always solves the problem for me. The data files are fine. The problem is characterized by starting up the initial files in my system and then having FileMaker suddenly quit, not unlike Geoffrey's problem. After this happens, FileMaker will not do otherwise no matter which files I attempt to open. I agree that there's an enormous difference between the program and the data and that, theoretically, the application ought not be damaged, but somehow it is. While this happens on my Mac, it has also occurred on several of the Windows machines on our network. Once it happens, no remedy other than reinstalling FileMaker works. My only explanation is that somehow FileMaker and our network's antivirus engine don't get along. This problem began about the time our network people made major changes to the antivirus system, which may install software on local workstations. Unfortunately, I have no input about the administration of our network. Geoffrey, just to make certain: You aren't running FileMaker Server, are you? And I assume that each copy of FileMaker is properly licensed. If so, Walt's suggestion about hosting the files is the way to go. And if that doesn't help, I'd still suggest reinstallation. Gary > Subject: RE: Ebase won't run on W2K machine > From: "Walt Daniels" <[EMAIL PROTECTED]> > Date: Mon, 12 Nov 2001 14:15:38 -0500 > X-Message-Number: 8 > > > > As for your problem, FileMaker sometimes becomes corrupted when networks > > misbehave. Occasionally, > > I, or one of my users, will have a problem similar to what you describe. > > Uninstalling and reinstalling the FileMaker application usually > > solves it. I > > assume all your files are set multiuser. > > > There is an enormous difference between FileMaker (the program) and eBase > files (the data) being corrupted. Crashes almost never cause corruption of > programs because once installed the files are never modified. Similarly > reinstalling programs that fail rarely fixes things unless other programs > have been installed after the one which you suspect of failing. It is not > unusual for the install of a new program to cause the failure of programs > that previously worked. The only cases where I have seen a reinstall to be > beneficial are for MS products which heavily use the registry which is > suseptible to the same kinds of corruption as FileMaker database files. I > don't believe FileMaker depends heavily on the registry. > > ------------------ 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 ---------------------------------------------------------------------
