OK...I'll buy that to a degree, but in this case, why use VFP at all? If you are going with the browser metaphor, why not just go straight to Visual InterDev?

>Envision this scenario. Your users work in very small organizations with stand alone computers, and little likeihood of ever hooking to an in-office network because they are, for example, small non-profits. An end-to-end VFP app is appropriate. Furthermore, your users are not extremely computer literate, and may perhaps be part-time volunteers. The only commonality of experience they might have is experience on the internet, perhaps ordering something or managing a personal financial account. Therefore, you move them several steps up the learning curve if the VFP application has the appearance of a web app. If it runs within their browser to boot, they feel more at home. Add to this the possibility that the application may one day be available over the web as a real internet app (i.e. the rent-an-app concept/re-written, not ported), and that you'd want a smooth GUI transition from the stand-alone to the web app.
>
>Therefore, the active doc can have usefulness to give the impression of a web app.
>
>ISC