I had someone setting up our database and notice that they created
and sent a number of emails to which they assigned source codes that
are not consistent with the source code protocol as we have set it
up. I'd had the impression that the source code protocol would
dictate which source codes could be used, partly as a way of
preventing confusion. The problem is with levels one and two, not the
two levels assigned to dates.
Anyway, those non-compliant source codes have been used and they
appear in the drop down boxes for selecting messages.
What's the thinking? I understand you must know the password for
creating source codes but I don't want to prevent most users from
creating new, repeatable messages. I do want to hold them to the
logic of the protocol we've established.
--
Simply,
John
mailto:[EMAIL PROTECTED]
http://simsoc.org
Thank you for you!
------------------
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
---------------------------------------------------------------------
