I have an app that will send out an email periodically.
My table has one row and three columns: a primary key, an "EmailFrom"
Address and an Email template.
The template is the text of the email and will have varying amounts and
dates in each one sent.
The template looks similar to this:
"Check # (########) in the amount of ($9,999,999.99)
was received and deposited on (xx/xx/xxxx).
Please direct any questions to DeptHead@compan y.com"
What is the best way to store this form letter template in an Access
app? Right now the three items are stored in one row of a table. While
that makes editing the form easy for the user, what is the best way to
allow them to edit the template, yet be able to easily plug in the
amount, check number and date without storing the templates multiples
times due to data changes.
Right now I am breaking this template up into chunks.
Fixed text, followed by a concatenation of field#1, followed by more
concatenation, etc.
I'm sure there is a better way to do this. (??)
*** Sent via Developersdex http://www.developersdex.com ***
My table has one row and three columns: a primary key, an "EmailFrom"
Address and an Email template.
The template is the text of the email and will have varying amounts and
dates in each one sent.
The template looks similar to this:
"Check # (########) in the amount of ($9,999,999.99)
was received and deposited on (xx/xx/xxxx).
Please direct any questions to DeptHead@compan y.com"
What is the best way to store this form letter template in an Access
app? Right now the three items are stored in one row of a table. While
that makes editing the form easy for the user, what is the best way to
allow them to edit the template, yet be able to easily plug in the
amount, check number and date without storing the templates multiples
times due to data changes.
Right now I am breaking this template up into chunks.
Fixed text, followed by a concatenation of field#1, followed by more
concatenation, etc.
I'm sure there is a better way to do this. (??)
*** Sent via Developersdex http://www.developersdex.com ***
Comment