As someone else (invariably) suggested, take a look at Rick's Westwind website. The whitepapers are fantastic resources. There are many ways to do it depending on what equipment is used (both client and server ends of it) and requirements are.

As each new suggestion came up from various resources on this same topic, I used them in a couple of my webapps. The ones I use (depending, again, on requirements) mostly are using a VFP COM server that the Web Server calls from a webpage (ASP usually) and returning:

1) an array that the ASP page can manipulate and show the user itself.
2) an HTML string that I create from within the VFP COM server itself and then:
a) pass the string back to the calling routine from the ASP page.
b) write the HTML to a file and direct the client browser to that newly
created page to view it.
3) an XML string that:
a) identifies an XSL file that the ASP page should use BEFORE sending
the XML to the user.
b) gets sent to the clients browser and the client browser can choose
an XSL file to view the data the way they want.
4) an ADO object that the ASP page can mess with.

I mainly use 2) or 3a), myself. It's really easy and flexible (and FAST with Foxpro) to make your own HTML strings from cursors and other return results before returning them to the user in some form.

- A Hilton





>Hello everyone. It's been a long time.
>
>I am currently doing work for a township assessor's office. They use a system that records property information for tax purposes. The current system is written in dBase, and I am rewriting it in VFP. They would like to have a web interface where people can go and view the record(s) for their address.
>Since the VFP app is just now entering development, I was thinking of temporarily converting the existing dBase database to a VFP format, then writing a VFP program that will search it and return the results. My question for you is: What's the best way to return information in html format, or a format that can be hacked up to be displayed on a web page?
>
>Thanks!
>
>j