Is there any reason to keep all the _old.102 files? I'm still using ebase 102, but for every file, there is a corresponding _old (I assume from when I converted from the really ancient ebase a year or more ago). Do they have any function?
I expect you are right, these files are a legacy from the
conversion from FileMaker version 4 to version 5. The only reason to
keep the files is as an archive, and there are good reasons to take
them off the active machine. Copy them to a removable disk and file
them away.
Also, since I'm doing some housekeeping, I have several copies of ebase on my hard drive, renamed after crashes (I've always renamed and saved the crashed file) and then recovered using a backed up copy. Does anyone see any reason to keep this stuff around?
Again, only as an archive, and these files _really_ should be
removed from your active machine. Filemaker can be pretty creative
about finding a workable file if the one it's looking for isn't
available. For example, you crash, damage a file, and FileMaker finds
one in another directory and opens it instead. You are working with a
mixed file set and don't know it. Copy to a removable disk and toss
them from the hard drive.
Is this stuff like 'mourning'... you hang onto it for an appropriate period and then try to let go?
I guess, but in this case, they can come back to
haunt you. Exorcise them.
------------------
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
---------------------------------------------------------------------
