>>FWIW, I have never tried this because it doesn't make any sense to me, for the same reasons that ActiveDocuments don't make sense: If your browser application requires components to be installed on the client machine, what is the advantage to using a browser interface at all? Why not build a VFP interface?
>
>I understand your reasoning here and it may prove necessary to do that.
>
>However, the issues for me are that:
>
>1) the client would like this to be implemented thru the ( Intranet ) web;
>2) we are dealing with 100's of machines here, pre-installing a small DLL control on all of them is relatively simple and straightforward here by running a script when they log into the domain, installing VFP and/or VB runtimes is a bit more involved ( but will be done if needed )
>3) I need this particular functionality ( i.e. automatically retrieving user info ) for security reasons to preclude abuse and so must have some kind of control to implement it if we indeed continue on this path
>

Bill,
I know you said you wanted this to minimize on abuse (someone logging into the site using another person's name) but (and this may be late in the game) why not enforce an NT secure login to access the site.

You could get the user name and password from a simple HTML form and using VFP, VB or VC++ at the server, you could verify it against NT security files that this was the correct username and password for that user. If they know this information then they could just as easily log into their local PC using it as well as your site so the chance of abuse is the same.

Rick posted a snippet of code not too long ago about how to verify a username and password. If you can't find it with a search, I have it printed out somewhere and I could send you the thread number. I think it was under WinAPI.