>My company is looking at WW Web Connection to build browser pages. We're a VFP shop and want to leverage our expertise. Can the Web Connection visual classes be set to _not_ generate HTML, allowing us to use the same code base to drive distributed apps as well as web browsers?
>
>TIA,
>Thom C.

Kind of, sort of. There aren't any actual "visual" WC classes (eg. no standard VFP form controls). WC does have a class that, when passed an object reference to an existing VFP form, can render a DHTML version of the form. This only works for browsers that support DHTML. You won't, however, be able to just take a standard VFP form and run it through these classes and expect everything to work the same (sorry, no silver bullet here). However, you could build a common UI layer that your web app. inherits from. Your normal VFP desktop app. would also inherit from this UI layer. Then you can customize the UI code according to how it's deployed. For example, you have a form named "CustomerForm" in a class library. You subclass this into a WebCustomerForm and a DesktopCustomerForm. Now you can make a change at the "CustomerForm" level and they will automatically make it into both subclasses.

Hope that makes sense - it's a seemingly simple question with a complicated answer <g>