Rick, thank you for your very complete answers. Over the weekend I downloaded your sample version, and have it running. Now it's time for experimenting. Easy to setup, thanks to your complete documentation!!

Thanks again
Barbara

>Hi Barbara,
>
>>Fairly simple - straight data entry, but there's a lot of branching: If I enter '1', I get these 3 questions. If I enter '2' I get 4 other questions.
>
>I think either product will fit the bill, since it sounds pretty straight forward.
>
>
>Since you are building
>a VFP GUI app also, you might find Web Connection's HTML Form rendering from running VFP forms useful.
>Most forms can run as is in Internet Explorer 4.0 (only at this time/Netscape 4 will be supported when
>they properly support Dynamic HTML and Cascading Style Sheets) and can update underlying
>databases with as little as 10 lines of code for the full updatable Web interface to a form. Note that
>this will vary with the complexity of your form's logic paths - the more options on a form the more
>external code you have to write.
>
>In this scenario you can keep most to all of the app logic in your existing forms and add only a
>small external inteface to these forms, so that they can be controlled from the Web interface.
>This would be things like navigating the form to the correct record/entry, putting it in editmode,
>saving etc. IOW, your typical business object logic driven through an external interface not unlike
>controlling a BO from the command window. That business object would then be driven by
>the Web interface with very little code that only decides on what to run next, but not *how* to do it.
>
>The above only works with IE 4, but it does give you full support for most VFP GUI objects including
>pageframes, grids (read only) and nested containers rendering in visually accurate x/y positioning.
>There are some problems with IE401 unfortunately - MS has broken some of the layering code in IE401
>that causes layered pages (in pageframes) to not clear all objects (lists, popups and grids), but
>that should get fixed in the next maintainence release of IE 4 (and it does work correctly in the
>original and beta versions of IE 4). For single page forms there's no problem.
>
>If you can't work with IE 4 WC also has a ton of tools to simplify taking your interface to the
>Web, but it'll obviously be more work as you'll have to design your forms in HTML. If you do
>you can databind these forms to Web Connection using external pages created with FrontPage
>or other HTML editor, or create static pages or create pages entirely in code. Your choice <s>...
>If you choose to use 'dynamic' external pages you can use FoxPro code in those forms using
>the scripting engine built into Web Connection.
>
>As output is concerned there are tons of tools to help you with quickly creating HTML from
>cursors, records and render them as HTML, lists or popups or other form controls - mostly with
>a single line of code.
>
>To see some of the samples that come with Web Connection to use in your own apps visit:
>
>http://www.west-wind.com/wconnect/
>
>All samples come with product and you can view the code for each of them right online by clicking
>on the Show Code link.
>
>Regards,
>
>+++ Rick ---