At 10:15 AM -0400 4/18/01, Carl Paulsen wrote:
>Remember that if you use Source Codes (and depending on how), you can
>have a record of the communication stored with the source code in the
>form of the text field. You don't have to use that method of actually
>producing the contact piece in order to keep that as a record - just
>copy and paste text from another application into the text block and
>voilla! you have a record.
If you use a source code, I know it can be used for multiple use of
an identical message. Are you saying that more than one message can
be stored under the same source code and that the actual message can
be recalled when you check the contact record? And, if this is so,
would it also work if you pasted incoming messages into the field?
>Then, of course, you could modify the source
>code "buckets" to flag them for level of importance. (You don't need to
>use ebase's canned coding system.)
I'm not clear on what a bucket is, nor on how you flag one for level
of importance.
>This would work for future
>communications, but it would be a bit of work to change old
>communications to fit the new source code structure.
--
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
---------------------------------------------------------------------
