Beware that if ebase has been using some of the recovered files to hold some of the data (for example, it could use the Payments_recovered.100 file to hold payment info and not payments_.100). If you import from the payments_.100, you may find you're missing some data. To sort this out could take some work, but things would be much easier if you did that work first.
Carl Dave Shaw wrote: > > >Subject: Multiple questions - please help! > > > > > >In April, I inherited an ebase program in poor shape, and was wondering if > >anyone could help me out with some solutions for these problems on my 1.03 > >version. > > > >1. All my file extensions are .100, but I have files named names.100, > >names_new recovered 2.100; two files identically named custom_.100, custom > >recovered 3_.100, customR3_.100,custom recovered 3 recovered_.100 . Backups > >were sporadic, and my back-ups would contain all this hodgepodge of info. > >Any cleanup ideas? When I tried to delete what I think are the obsolete > >files, ebase tells me it needs them to open something. This is true with > >almost all the files. How can ebase run so many different files? How do I > >instruct ebase to recognize only those files I identify, or do I somehow > >merge these files into one???? > > > > The files named something_recovered.100 relate to a previous crash > and recovery. In your case where there are also files names > something_recovered 2.100 it looks like this has been done more than > once. There are several implications. First, the recover procedure is > faulty, so the procedure recommended is to recover the files to get > access to the data them migrate the data to a new, clean set of > files. Also, apparently ebase is using some of the recovered files, > since you get asked for them when you attempt to delete them. This > resulted from an error by the user who recovered the files. Overall, > I think the only way out is what Walt suggests, open up a new, clean > set of files and import the data from your existing file set to the > new one. Use the FileMaker import command, and import the data from > each file to its matching new files. When asked to match fields, tell > it to match field names. The only other caution is that you need to > reset the auto-number index in the files with auto-numbered record id > fields to avoid duplicating numbers. > > -- > -- > 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 > --------------------------------------------------------------------- -- 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 ---------------------------------------------------------------------
