I'm trying to find out the best architecture would be for a web+access
solution. We have a database of individuals' job details. There's a big
table with an ID key field, name addess etc, and a whole load of fields
that depend on other tables for their options. We wish to allow the
indivduals to update their record over the web. They must not be able
to access anything other than their own record. We have a lot of
queries and reports we use on this database and we'd like to keep it
running on Access for this reason.
Ideally what would happen is that every few months an automated process
would send an email to an individual containing the data we have on
them. The email would have two links, one to indicate the record is
up-to-date, the other would take them to an update form.
One way I thought we could do this is via some scripts running on the
database server. This would not be a web server, it would generate a
form which got uploaded to the web with a unique URL. This would
provide some security, possibly enough for us as we want to avoid
passwords. When the form got filled in it would somehow send it's data
back to the database server and be incorporated to the DB.
This is purely speculative, and I don't want to do it myself, I don't
have time to learn the skills (though I would like to be able to make
minor changes once it's up and running). What I need to find out is the
most sensible architecture for a solution.
Can anyone advise me?
Thanks,
John