>...and as a follow-up question (sorry I forgot to include this in my original message...
>how could the ASP / ASP.NET page 'know' that a VFP COM Object/DLL is installed locally as opposed to on the server? Is it simply where the DLL is 'registered', or is there more to it than that?


Hi, Kevin... let me try to answer your questions:

ASP is a server-side tool, not client-side. So, everything runs on a server. I think you can install your DLL in your client machine (with VFP runtimes, of course), and use it on the client-side with JavaScript or VBScript, BUT, you´re tied to Microsoft clients... another problem: it´ll be like hell to update your DLL on every single client...

personally, I never saw nobody doing such thing...