Bonnie,

Browser-based applications, and I can say this with limited web application experience myself, are TOTALLY different than your regular VFP desktop application.

You don't have the luxury of a "OK" button or a QueryUnload() where you can tidy up before leaving... the operator decides when they want to leave and it can be during mid-typing in an entry field. "Stateless"! You can do some entry validation in the browser but you probably also need to do the same in the processing itself to be safe. This means 2 distinct places to be changed whenever some 'rule' changes.

I found my few interesting to do and I certainly needed the help of a skilled HTML/CSS/??? person to get the job done.

There may be good reason why your client wants to go browser-based, like maybe sending everyone to work from home to save office expenses < s >

Taking your words literally I'd have to say it **IS** a total re-write of at least your UI parts, with radically different logic governing table updates.

good luck


>This may be a basic 'stupid question', but here goes:
>
>I've been developing VFP desktop apps for years. Lots of really cool apps with really involved UI's/business logic etc. The apps are currently in VFP8 (back end data and all).
>
>Now my users are hearing 'intranet' and wanting to move everything to browser based apps.
>
>This is my question. My clients seem to think that *every* app is better off running on the web. I am thinking that some of these apps can't run on the web because the UI is too involved and complicated. Am I missing something? I've never seen an interactive web site that does field level validation and many of the other great vfp features.
>
>There is no such thing as 'converting' a vfp desk top app to web is there? It's a total rewrite no matter what language I use. Is that correct?
>
>thanks
>
>bonnie