Renewal letter system
I am trying to do a letter renewal system, but I just cannot seem to get my
head around how to accomplish this task and would very much welcome some
advise.
What I have done so far: -
The user creates their own letters in word (which I use to mail merge) and
I store the file name and location to a table.
The user will then set up a criteria for this letter i.e. age range , medical
condition. which I use to filter the data. So far so good this all works.
My problem is: -
The user creates lets say Adult1.doc I then get the data I need for Adult1
and do the mail merge (again all ok) but. If the customer does not reply
back to the letter in 3 month another letter must be sent but a different
letter this time it would be Adult 2 .doc and this happened 5 times so
5 chase letters in total. This is where is am stuck as I am not sure how
to accomplish this. As the user creates the letters them self.
This would also apply to different chase letters i.e. Child 1 so if they
set up a child renewal and set the criteria for this I need this to do the
same thing. There would only be 1 chase system per customer.
I am sure that most of you have done something similar and would welcome
any pointer in the right direction on how to proceed.
Sorry if this is not to clear but trying to put this into words is just as
difficult!
Many thanks
Paul
# 1 Re: Renewal letter system
On 8 Sep 2003 06:40:07 -0700, "Paul Summerfield"
<fox@quantumistic.co.uk> wrote:
>The user creates lets say Adult1.doc I then get the data I need for Adult1
>and do the mail merge (again all ok) but. If the customer does not reply
>back to the letter in 3 month another letter must be sent but a different
>letter this time it would be Adult 2 .doc and this happened 5 times so
>5 chase letters in total. This is where is am stuck as I am not sure how
>to accomplish this. As the user creates the letters them self.
I'm not sure what the question is. Sounds like you need to have a
table that keeps track of the letters to be sent (storing file names)
and some way to mark each customer with the type of letter they're to
receive and whether they've responded.
Tamar
# 2 Re: Renewal letter system
"Paul Summerfield" <fox@quantumistic.co.uk> wrote:
>
>I am trying to do a letter renewal system, but I just cannot seem to get
my
>head around how to accomplish this task and would very much welcome some
>advise.
>
>What I have done so far: -
>
>The user creates their own letters in word (which I use to mail merge) and
>I store the file name and location to a table.
>
>The user will then set up a criteria for this letter i.e. age range , medical
>condition. which I use to filter the data. So far so good this all works.
>
>My problem is: -
>
>The user creates lets say Adult1.doc I then get the data I need for
Adult1
>and do the mail merge (again all ok) but. If the customer does not reply
>back to the letter in 3 month another letter must be sent but a different
>letter this time it would be Adult 2 .doc and this happened 5 times so
>5 chase letters in total. This is where is am stuck as I am not sure how
>to accomplish this. As the user creates the letters them self.
>
>This would also apply to different chase letters i.e. Child 1 so if they
>set up a child renewal and set the criteria for this I need this to do the
>same thing. There would only be 1 chase system per customer.
>
>I am sure that most of you have done something similar and would welcome
>any pointer in the right direction on how to proceed.
>
>Sorry if this is not to clear but trying to put this into words is just
as
>difficult!
>
>Many thanks
>
>Paul
>
