A local browser cache copy of the data would certainly be fine, as long as you also have the business, event and UI layers logic sitting next. This would mean translating / converting the whole VFP code in javascript.
Translating code sounds a bit like Esperanto to me.
;)
>In Q1 I was traveling by train quite a bit over europe - I was very happy to work offline ;-)
>But for new dev I probably will often argue for including only an option to work with a HTML5 local browser cache copy of the data.
>And this translates to replication into SQLite from my POV - which could probably be generated from your architecture,
>but not as it stands now. Just my idea where to develop next, if your approach sells enough.
>
>regards
>
>thomas
Thierry Nivelet
FoxinCloud
Give your VFP application a second life, web-based, in YOUR cloud
http://foxincloud.com/Never explain, never complain (Queen Elizabeth II)