Okay. I can understand duplicating records and transferring payments would
work. Fortunately, as you said , it's not necessary in this situation.
I'm wishing I'd logged on to this support months ago though, because I'm
gleaning so much information from all the various problems people have.
Questions I hadn't had yet, but probably would have had sooner or later.
But also, the notes back and forth help give a more rounded understanding of
the program.
Yes, I'd read the ebase administrators manuel all the way through once, and
then parts of several times. But there's a lot I either missed or wasn't
addressed in the manual.
Thanks to those of you that are so willing and able to help out others!
Lisa
-----Original Message-----
From: Dave Shaw [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 9:28 PM
To: TechRocks Support
Subject: [support] RE: double record numbers
Gary, good catch. I see that there was indeed only one dupe record
with payments in this case. If I had to recover from a more serious
situation, I would duplicate the troublesome records to create
another record with a valid record number then use the transfer
transactions function to move the payments and other related records
to the new record.
>A Warning - Be careful deleting records with duplicate record numbers.
Since
>FileMaker doesn't know the difference between the two Name records, as you
>have already noticed, it will happily delete any and all related records
>which are set up for automatic deletion with the parent record. This
applies
>to *either* of the duplicated records.
>
>So let's say you have a legitimate record for Ms. A with 2 dues payments
and
>a large contribution. Then you add Mr. B, with the auto-numbering
mistakenly
>assigning it the same number. Now Mr. B also appears to have made the same
>payments, even though he really just bought a bumper sticker. When you
>delete Mr. B's record in the Names file, it may also blow away Ms. A's
>payments, since they are linked by the same Record Number. I'd suggest you
>check. It may be necessary to re-enter all the payments (and any other
>details) for the original record after deleting the dupe.
>
>There are sometimes easier ways of handling this if you know about the
child
>records before deleting. In this case, the ebase programmers seem to have
>done such a great job of enforcing the integrity of the Record Numbers that
>adding back related records appears to be the easiest way. Dave, have I
>missed some clever workaround?
>
>Gary Bogue
>
>> Subject: RE: double record numbers
>> From: "Roland and Lisa Morris" <[EMAIL PROTECTED]>
>> Date: Sun, 4 Feb 2001 22:00:35 -0700
>> X-Message-Number: 1
>>
>> Thanks Dave,
>>
>> That was exactly the problem and I have it all fixed now.
>>
>> Now just to clarify; I don't see an export function in the ebase
program.
>> A function for sending all or part of the names and addresses to someone
>> else for use in a mailing.
>>
>> So although I am not to use the Filemaker IMPORT function on the drop
down
>> menu, I still need to use the associated EXPORT function to send stuff
>> out,
>> right ?
>>
>> Thanks,
>> Lisa
>>
>> -----Original Message-----
>> From: Dave Shaw [mailto:[EMAIL PROTECTED]]
>> Sent: Saturday, February 03, 2001 10:45 AM
>> To: TechRocks Support
>> Subject: [support] Re: double record numbers
>>
>>
>> Record numbers are auto-entered when a new record is created. The
>> next number to be used is set in the field definition and updated if
>> you add a new record, BUT when you import records you need to re-set
>> this index to a record number higher than the largest in your import
>> set. If you use the ebase import routine, this gets done for you.
>> Apparently you used the FileMaker menu item to import.
>>
>> So, delete the records with duplicate numbers. Find the highest
>> record number (by sorting the records by record number, for example).
> > Go to the field definition for Record Number and check the Auto-Enter
> > tab. You'll see that it's checked to auto-enter, increment one. You
> > should set the Next Number to one higher than the highest record
>> number in your file.
>>
>> Now when you enter new records, the will be numbered higher than the
>> ones already in your file.
>>
>>
>
>------------------
>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 Northwest Classics, Inc
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
---------------------------------------------------------------------
