I'd still like to know an answer to this one. I suspect the thinking was
that with custom emails you would want to customize the subject line. But
when you're sending 1500 emails that's impractical.
Maybe both John and I are misunderstanding it. Anyway, John, I'm going to
muck around this week on it and when I find a workaround I can send you a
walkthrough. It's probably just a matter of some layout tweaks and script
steps.
Colin
on 12/3/00 5:03 PM, John Watkins at [EMAIL PROTECTED] wrote:
>>> I've set up a source code record for an email. Have used the
>>> description line for the subject line. When I generate an email
>>> however, there is no subject line. Obviously the subject line is
>>> very important. How do I get the subject line to come up
>>> automatically?
>>
>> I can't get ebase to behave as you describe. All the options I
>> choose for selecting source code text and entering a subject line
>> result in email(s) with the subject line I have entered. This is
>> probably why you haven't heard an answer - no one can figure out
>> what's wrong. Can you describe in excruciating detail what you do
>> and what happens to make it act the way you describe?
>>
> You asked for excruciating detail, so here it is.
>
> We have a number of different emails that we use in various stages of
> volunteer and member recruitment. It is often necessary to send them
> out to a found set in excess of twenty at a time.
>
> The subject line needs to be appropriate to the message and we need a
> contact record for each person who receives the message.
>
> Using source code AA, we want to encourage people to "set up a chapter".
>
> If I choose - "select an existing source code and text", and select
> "batch," I get a single email message with a blank subject line. I
> then have to type in the subject line and paste the email addresses
> into the bcc: field. That's OK because I can make a contact record
> with this.
>
> But, I prefer to address each person individually--it produces much
> better results. If I choose "custom", ebase does make contact records
> but it generates separate, individually addressed emails, none of
> which have a subject line. To add a subject line, it's necessary to
> open each message and insert a subject line--a tedious and
> time-consuming, time-wasting task.
>
> If, on the other hand, I choose "copy text from an existing source
> code record,"
> I'm presented with a screen that permits me to enter the subject
> line. The next step is the choice of setting up a new source code. I
> really don't want to create a new source code, so I choose "no, just
> proceed to the next step." Eventually, I have the choice of "batch"
> or "custom." Batch isn't acceptable. So I move on the "custom."
>
> It then asks me if I want to create contact records now. I do, but to
> create contact records, the program requires that I set up a new
> source code. Setting up a new source code is problematic because I'd
> be adding a new source code at least once a week for exactly the same
> message. That would get quite confusing and it wastes more staff time.
>
> This does generate individually addressed messages with already
> inserted subject lines--but no contact record.
>
> I can see one possible work around. Generate the contact record but
> not the email using "select an existing" and then separately generate
> the email but not the contact record using "copy text from."
>
> Why isn't it possible to generate the subject line when you create
> the original source coded email? Failing that, why is it possible to
> enter the subject line once on one path (copy text from) and not on
> the other?
>
> So, is there an easier method than the work-around I suggested to
> generate multiple email message, each addressed to an individual,
> each with the proper subject line, and each recorded as a contact on
> the individual record?
>
> Is that excruciating enough?
