Dave Shaw kindly responded
>You're not clear what you're looking for, that is, what an 
>acceptable solution would be, so let me suggest some.


Thanks for trying. It IS sometimes hard to explain.

>>If we send a scratch letter, to make a contact record, it requires 
>>that we create a code. If we create a code, each code shows up in 
>>the pull down box from which you select previous records.
>
>There is a workaround that I'm pretty sure Jack Noll published in 
>the FAQ. It's at least in the list archives. It involves flagging a 
>new source code to appear or not in the pulldown list. You change 
>the value list to select only the flagged items.

Can you or anyone be more specific about where to find this fix--or 
even better, just send it to me. I tried to find it in the FAQs and 
couldn't.

I don't know how to find the archives. Maybe that would help but I 
suspect it's like searching for that "needle in the haystack." 
Except, with the needle, you know what you're looking for. A needle 
is very specific and :>) to the point. With a problem, you don't know 
what the answer is so it's not easy to find the right search 
process--what words describe an unknown answer?

>>If we choose "select an existing source code and text", you can't 
>>make changes and it produces emails without subject 
>>lines--inserting the subject line in more than one email is 
>>difficult to say the least.
>
>I'm not sure the interaction of ebase and your email client can be 
>made this flexible.

The user manual really makes a strong point of how important the 
subject line is to the success of your contacts. I couldn't agree 
more. So it strikes me as strange that the program doesn't provide 
for automatically filling in the subject line when generating 
"custom" messages to a found set. Nevertheless, the temporary answer 
probably lies in sending batches. Even here, it's necessary to 
re-type the subject line.

>For work at this level you should be looking for a consultant who 
>knows how to program the system-level automation utility. It's 
>called Applescript on the Mac - don't know what it's called on 
>Windows.

Truly, I suspect many of the users of have chosen Ebase because they 
have neither the resources nor the knowledge to work with a 
consultant. That's true in our case. Our problem is to recruit and 
work with a large number of volunteers, with very few dues-paying 
members--at least for the foreseeable future. Maybe, we can find a 
volunteer to do the work but that has it's own problems--continuity 
for one (can they volunteer enough time and will they see the job 
through to its conclusion) and our inability to determine if they 
truly know what they're doing

At any rate, if anyone can find and send me the "fix" for keeping 
some source codes out of the drop-down list, I'd be in your debt.

-- 
  simplicity ~ personal responsibility ~ compassion ~ community ~ justice
           a unified process for developing full human potential

           John Watkins  Executive Director  The Simple Society
             303 Amherst St.  Nashua, NH 03063  603-889-0111
                   [EMAIL PROTECTED]  http://simsoc.org

Reply via email to