As Dave suggests, the problem appears to be that you have duplicate record numbers for many records in ebase. You can check for this by doing a find for duplicate record numbers. Click the Find button, enter and exclamation point (!) - without the parentheses - into the record number field (the blue number at the top of the Home screen) and see if you have duplicates. I assume you'll find many.
Based on what you've said about how you imported records (everything sounds OK), I can only think offhand of one thing that might have caused it. If someone imported records into ebase a while ago without using the ebase import routine (most likely during an upgrade from an earlier version of ebase) and didn't re-set the record number counter, it could be that you are re-using record numbers already in use. You should fix this problem before entering any more data in the database. To do it you'll need Filmaker. And before you start, always make a backup of the database so you can at least get back to your current data. Probably the easiest way to do it would be to go back to a backup of the database that preceeded your import and re-import the data. Before re-importing, however, check for duplicate record numbers (see above) and if you find any, fix them (see below). Once that's fixed, you'll need to re-set the record number counter for the record number field. This entails first making note of the highest existing record number in the database (make sure your database is unsorted, scroll to the last record in the rolodex, and note that record's record number). Next, go into the Filemaker menu File->Define->Fields, select the record number field and select the Options button. In the auto-enter option, make sure to set the counter to at least one number higher than the last record number in use. This will ensure that all new records that you add (by importing or manually adding records) will have unique record numbers. Lastly, re-import the data. If you don't have a backup that you can rely on, you may be able to fix the database by manually re-assigning record numbers for duplicates. If you're at all squeamish, perhaps you should get a consultant to help you with this, preferrably one with ebsae experience. The basic way I'd approach this is to find the duplicate record numbers (as instructed above) and change duplicates so that they are all unique. For any records that have a payment associated with them (the ones with the names at the top of the payment record), you want to keep the existing record number. All other dupes should get a new record number that is higher than the last number in use. Ebase comes with the record number field in an unmodifiable state, so you'll need to change that before you try to change any record numbers. Go into File->Define->Fields and select the record number field. Click Options and uncheck the box at the bottom that says "prohibit modification of value. Now you can re-assign record numbers. Be sure to use unique numbers for all the records re-assigned. If you know there should be payments associated with some of these records, you may need to do some extra work to fix those, but I won't get into that here. Inquire back if you think you have that problem. Do a final check for duplicate record numbers. If you find none, good job! Now you should immediately re-set the record number field to PROHIBIT modification. Lastly, find out what the current highest record number is that is in use, and re-set the record number counter to be at least 1 higher than the highest record in use. That should do it. Be sure to do lots of spot checks of your data to make sure everything seems correct. HTH, Carl Information wrote: > > I am importing into ebase that already has about 3500 records. I used the > ebase import routine. and I checked auto-enter options during the import. > and I have followed the steps in the manual a few times trying to do this > still with no luck. > Every time I open Ebase now, I see the records that I imported and still > when I go to their payment screen(which they shouldn't have since they > haven't given us payments) it switches to another member. > > Jessica Flipp > Dads and Daughters > 218.722.3942 > Fax 218.722.4058 > [EMAIL PROTECTED] > www.dadsanddaughters.org > > -----Original Message----- > From: Carl Paulsen [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 11, 2002 10:10 AM > To: TechRocks Support > Subject: [support] Re: importing records > > Are you importing into a "clean" copy of ebase with no records in it > already? Did you use the ebase import routine or the Filemaker Import > command? Did you select to perform auto-enter options during the > import? These questions are important to the answer. Finally, have you > carefully followed the manual instructions on importing? > > Carl > > Information wrote: > > > > I was just importing the names, I hadn't gotten to importing the payments > > because these people won't have payments. The ones that I am importing > from > > access are just names, no payments, and when they are imported they are > > given the payments of past members. and they are there when you look at > any > > of the screens except the payment screen. Once you hit the payment screen > it > > goes back to the past member and the member that was imported is now gone. > > Not sure what is going on. > > > > Jessica Flipp > > Dads and Daughters > > 218.722.3942 > > Fax 218.722.4058 > > [EMAIL PROTECTED] > > www.dadsanddaughters.org > > > > -----Original Message----- > > From: Dave Shaw [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, July 10, 2002 05:04 PM > > To: TechRocks Support > > Subject: [support] Re: importing records > > > > >I re-tried importing records, This time they import all the information > is > > >there. they have record numbers and everything. Except when you click on > > >view payments(which they shouldn't have) there is a payment there, only > it > > >has someone else's name and then when you click data entry they have > > >disappeared and it is like they were never imported.. I am not sure what > is > > >going on. > > > > Mis-matching the names and payment records is usually caused by > > getting incorrect data in the key fields, in this case the RecordID > > field in the ebase names and payments file. These fields are assigned > > by ebase as you import the data. When you map the data from your > > source file (an Access file, I remember?) map the unique ID number in > > your source file to Legacy ID both as you import names and later as > > you import payments. > > > > -- > > -- > > 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 > > --------------------------------------------------------------------- > > > > ------------------ > > 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 > --------------------------------------------------------------------- > > ------------------ > 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 ---------------------------------------------------------------------
