I think it's clearer. It sounds like you can search for contact records and find those that have the incorrect values? If so, quickly make a backup of the database and try this: create a new code with the correct values, R1A1001ROL and a description that slightly differes from the old Oct 01 description. Now, you need to find all the contact records and instances where you used the incorrect code and replace that with the new correct code. For example, you can go to the Contacts file (Contacts tab -> View Contacts) and search for the incorrect records. Do this carefully, becauase you don't want to get the contact records for the correct r1a1002rol code. This may entail searching on the code description field for the old October 01 code description. To do this, you may have to go into layout mode and set the field format to allow entry into that field. This is done by right clicking the field on the layout and selecting Field Format, and setting behavior to Allow entry (on a Mac, you get there by clicking Option-Apple-F).
You'll get a found set of contact records (not people, but the contacts attached to those people). Confirm that you have only gotten the offending codes and not the valid r1a1002rol code. Then, change one of those records to the new code and, with your cursor still in the source code field, select the FMP Replace command from the Scripts menu. Make sure it is going to replace the code with the correct code, then click OK. This should correct the code for all the bad contact records. You also need to do this in the payments file to make sure any of the offending codes weren't attached to any payment records. If they are, change them in the same way. Do the same for the Actions, Pledges and Notes files.
Once all of the instances of the code have been changed, you should be able to delete the offending code in the Solicit file (Admin->Add/Edit Source Codes).
Good luck.
Carl
Carolyn Servid wrote:
--Carl, Somehow I have ended up with a single source code that has two different sets of values and two different descriptions. When I look up the source code, R1A1002ROL, there is one description, OCT 01 RENEWALS, with values read R, 1A, 10, 01, RO, L. Those values, though just one number off, don't match the code. (And I don't know how that happened.) There is a second description, 02 SEPT/OCT RENEWALS that has the correct values for the code: R, 1A, 10, 02, RO, L.What I'd like to do is create a correct source code for OCT 01 RENEWALS that matches the values, and then correct the contact records Hope that makes sense. Thanks, Carolyn
Carl Paulsen
8 Hamilton St.
Dover, NH 03820
603-749-2310
[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
---------------------------------------------------------------------
