>Foxpro CGI??
That's what foxISAPI is (i think - but am often wrong:). The result of a post or get is written to an INI file on the "server" with names like "FOX1C.INI". IIS provides foxISAPI with a "session" id. CGI-COM then reads the contents of the INI file (i used to use FOPEN() a million years ago). Now file_to_string will do it. CGI_COM then assesses the contents and routes a reaction (return script). I think there's a guy called "GetProfile" - that also faciltates a read of the "post" data.

I think that kind of transaction is CGI.

Its clumsy - I just read some stuff in IIS help about ASP. YOU GUYS ARE RIGHT. It seems that ASP will contain the form results and [can] also instanciate my VFP "logic" COM. Which of course will get be out of the CGI-COM business and allow me more time for the "logic" guy.

But the client - and they host a bunch of servers and even use WC for some of their services - asked that I keep it as lean as possible. The only "technical" requirement (from the regulating/advisory body) is that the client (browser) be JS and Flash enabled.

So the client is a geek too! And I sugessted ASP (more than once) - and their response was that some of their users do not have ASP installed on their servers. And - that they would prefer not to have ASP as a requirement. With foxISAPI - only the CGI COMs would have to be registered.

You sounded surprised about the CGI "label". Is there a "store" for post data on the server that would eliminate my need to read INI files? The INI file is the only store I am aware of. And, INI file = CGI (or so i believe)!

You guys are correct - but despite my pleas, the marching orders remain the same:(.

This is not so much a database project as it a "DOM" project. When you have time check out "Shared Content Objects". The protocal and source is a mountain of JS,JSP and JAVA as well as PDFs - some with hundred of pages of edit change bibliographies (YUKOLA!). Is this what my life has come to - an operations researcher that can [also] write code?:) Life was a lot easier when I only had DBFs and indexes to contend with!