B
Bob Austin
To read the MSKB and slipstick.com articles, as well as postings here,
one-off forms sound like an evil to be avoided. For my solution, they seem
to make sense. I'd like feedback.
I'm dealing with a ~20 volunteers of a non-profit collecting data for 1000+
items over a few month period. Everyone has Outlook (used on home
machines), but not every is literate beyond the basics. Ideally, I'd send
them an email with a form that they could fill-in and reply to. I'd then
have the data to parse into Access.
In digging in here, it looks like a one-off form that gets sent with the
data is the way to go. I don't care about data size or long-term maintenance
of the form.
Am I on the right track here?
Re the RTF stipulation, will HTML work as well (or better)?
Bob
one-off forms sound like an evil to be avoided. For my solution, they seem
to make sense. I'd like feedback.
I'm dealing with a ~20 volunteers of a non-profit collecting data for 1000+
items over a few month period. Everyone has Outlook (used on home
machines), but not every is literate beyond the basics. Ideally, I'd send
them an email with a form that they could fill-in and reply to. I'd then
have the data to parse into Access.
In digging in here, it looks like a one-off form that gets sent with the
data is the way to go. I don't care about data size or long-term maintenance
of the form.
Am I on the right track here?
Re the RTF stipulation, will HTML work as well (or better)?
Bob