Hi Peter,

1- Thanks for liking this design -- to tell you the truth a design studio was involved in the project ... of course this form also shows up in the browser using FoxInCloud with an enhanced look & feel (using CSS & JS): https://www.dropbox.com/s/3gm7lzr99iustek/Capture%20d%27%C3%A9cran%202016-02-17%2014.25.03.png?dl=0

2- FoxInCloud uses WWWC as interface layer between the Web Server (IIS generally) and the application; the rest is pure VFP code, plus your application of course. FoxInCloud generates 100% standard HTML-CSS-JS, nothing or install or care about.

http://foxincloud.com/faq.php gives a lot more details about FiC architecture.

>Thanks for your info. It must be some idiosyncracy in the (selfmade) class I use for my grid. On init of the grid I replace Text1 objects with a special class textbox. Although I do copy all properties from the original textbox to the new one, vfp apparently gets confused by it. Probably the order of things is disturbed. So, I'll have to dig into my own special class code.
>
>By the way, nice layout of the app in the picture. I have also read more now about FoxInCloud. We have to send info to a web interface (requests and answers) and plan to do this with WW. Your solution goes even further. Problem here (KLM) is that they want all web applications to be built with one of a restricted set of applications. They do accept WW as 'intermediator' (receive requests, send them to vfp and return the answers to the web app). How about foxincloud? Can it fit in this scheme?