Ellen,

This really sounds to me like something that could easily be done with just ASP. As Erik pointed out, ASP code never gets to the client because ASP scripts always run on the server. You can easily use ASP to get the record from your Access database, calculate the new key, then store information on who requested the new key and when back to your Access table. ASP alone isn't as scalable as having ASP call a COM object but it sounds like this is something that people only do periodically so scalability may not be an issue.

>
>Here is how the entire process works:
>Each time they run my VFP program it checks to make sure they have a valid Auth Key. There is a VFP table that stores (encrypted), their Registration Number, their Authorization Key and some date fields. When their current Auth Key expires, a new Reg # is created and they need to get a new Auth Key. The Auth Key is based on a mathematical formula as well as who they are. Depending on the user, the Auth Key I give them will be either a demo key, a timed key or a permanent key.
>
>As I said, currently the generation of the Auth Key is a completely manual process. When they need a new key, they call me and I give them one based on their Reg #.
>
>When we automate this, we also want to track who and when they requested a new Auth Key. Currently there is an Access table that is checked before a user is allowed to logon to the intranet. I was thinking of just adding some fields to this table (dateOfAuth, DurationOfKey, TypeOfKey etc), however I could create a different table if necessary.
>
>I'm not sure of how to approach this whole task. I have never before set up a web app and I'm just trying to figure out how all the pieces fit together and what my options are. I am not the Webmaster, and don't know a lot about the intranet structure. I can find out whatever I need to know, but at the moment am not sure even of what questions to ask! :)
>
>Thanks for your patience!
> ~ellen