>Thanks Alex,
>
>Good suggestions and example. VFP runtimes are not required and I knew they would be a problem if they were.
>
>Mel Cummings

I use the XML approach at work for our Extranet. Not to allow users to post anything as in this example, but to allow users to change their language at runtime. We support three languages. The site is plain old ASP. The GetXML("tagname") parameter embedded as islands in the HTML allows the function to make a decision on which tag contents to display when rendering the page.

The XML file has the same name as the page in a subdir (i.e. "default.asp" has a corresponding ".\xml\default.xml"). The XML is simple. A node for each language we support. Then the same set of tags for each language with the translated strings. The function sees what the desired language is, knows where to find the file and looks for the tag under the proper language node. Magic translation on the fly in a web page!

For the form design to enter the text, look at the eBay example I mentioned. They have made it easy for anybody to create listings even including links to digital photos.

HTH