>I know it wasn't...
>
>Attached are two pics of what Eeva pages are like - one the design time and the other the browser time. It just BEGS being able to get ID Value pairs - lol!

The brackets he uses are just the same as Rick's framework uses, and that's plain old textmerge with different delimiters. That's the easy part and that's something you can write yourself, if your goal is just to produce html with plain text content.

It's the html with controls in it that's the tricky part - and that's where you need the request object, response object, post data, name-value pairs from postdata... even ways to do AJAX.

And the mention of .net stuff is not to be neglected - I have worked recently with a rather young guy (younger than my daughters) who did that part in c#, while I supplied a COM object built in Fox which he then uses. So I do all the database heavy lifting and marshaling data from and into tables, while he does the web stuff. We're both doing the parts that come easy to us :). And that's just a new version of a web app previously done using WWWC - and believe me this is much simpler. There are a few things you can't do from a Fox COM object, like calling a .ShellExecute() or creating a dbf, but other than that it just works and it's all very fast. So think of such a combination too.