J
Jack
I currently have a db that extracts a webform, queries db to determine who
needs the information, then emails it to them.
Currently the message body is set up in vb with text and the various
fields(30+) from the evaluation recordset. All of this seems to work fine
however I would like to ALSO base the message body depending on what website
the evaluation came from.
What I thought about doing was to create a table called messages and have it
linked to my current table called websites. Inside the message table I would
like to include all of the vb code that creates the message body.
for ex: website #1 would have email body from message#1 - Website #2 would
have message body #2 etc....
How can I get vb to know that the field is actual code and not text?
My goal is to have 1)the outgoing messages in access, 2) easily updatable.
Is there a better solution to this or does someone have any idea how I can
accomplish this? Currently since the messages are pretty detailed with 30+
fields and lots of text, my vb code is pages and pages long - it takes
forever to update a particular message not to menton all of the & and _
. I
believe my idea would drmatically reduce the lines of actual code if the
message body(s) were stored in its own table.
Any help would be greatly appreciated.
Thanks,
Jack
needs the information, then emails it to them.
Currently the message body is set up in vb with text and the various
fields(30+) from the evaluation recordset. All of this seems to work fine
however I would like to ALSO base the message body depending on what website
the evaluation came from.
What I thought about doing was to create a table called messages and have it
linked to my current table called websites. Inside the message table I would
like to include all of the vb code that creates the message body.
for ex: website #1 would have email body from message#1 - Website #2 would
have message body #2 etc....
How can I get vb to know that the field is actual code and not text?
My goal is to have 1)the outgoing messages in access, 2) easily updatable.
Is there a better solution to this or does someone have any idea how I can
accomplish this? Currently since the messages are pretty detailed with 30+
fields and lots of text, my vb code is pages and pages long - it takes
forever to update a particular message not to menton all of the & and _
. Ibelieve my idea would drmatically reduce the lines of actual code if the
message body(s) were stored in its own table.
Any help would be greatly appreciated.
Thanks,
Jack