Dear experienced users who remember ebase .100 ....
I'm working with a group that still has .100. We've run into a problem
creating and using source codes. Upon closer inspection, it was discovered
that in most ebase files (contacts, solicitations, pledges) the value list
for source codes was defined as a couple of fields out of the solicitation
table. However, for whatever reason the value list in the PAYMENTS file is
a custom list, with typed-in values, which just happen to be a subset of
the values in the fields in the solicitation table.
I looked at my own implementation of .102, and saw that the way the source
code value list is defined for PAYMENTS_.102 is analogous to the way it's
defined for contacts, solicitations, and pledges in the implementation of
.100 described above. In other words, it's _different_ than the way
PAYMENTS is handled in that implementation of .100.
Seems to me that it shouldn't be a problem at this point to just switch
the way the value list for source codes is defined for the PAYMENTS file in
.100 in the implementation I've described. We'd be changing it from the
custom typed-in values to being based on the fields in the .100
solicitations file. Since all values in the custom list are already in the
fields in the .100 solicitations file, we shouldn't be leaving any 'orphan'
source code values in the PAYMENTS file.
Can anyone think of a reason NOT to do this switch (and why?)???
If ebase .100 was not the odd way it's implemented here to begin with,
would you have any idea how/why it got changed?
TIA for any light you can shed on the subject!
Cheers,
Eric Johnson
Colorado Environmental Coalition
------------------
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
---------------------------------------------------------------------
