>Yes but that's only 1/2 the trick. Real question is how much re-working of a VFP project would be required to get it to run in Visual FreePro. If you can use the exact same source code then you'd really have me (and I assume a lot of other people) sold on the idea.

IMO, that's precisely the reason why Rick needs some other's help and insight.

Based on my experience as FoxInCloud designer and developers, there are many, many things that seem difficult if not impossible to support at first and, after a discussion with other developers and users, some night and bus thinking, you realize you can support.

You can find solutions to almost anything.

On example is supporting PUBLIC variables in FoxInCloud (as any web application, FoxInCloud has to save the user's context on each request, and public variable obviously hold part of the user context);

Initially, it seemed impossible to know which variables are PUBLIC and just save those.

After further thinking we realized that, when running a procedure or method 'above' the application, and provided FoxInCloud makes no use of PUBLIC or 'PRIVATE' variables, all the variables in scope (except LOCALs) are PUBLIC.

Then a simple SAVE TO ... EXCEPT saves over 1,000 PUBLIC variables in less that 10ms.

I think the real question is more of a strategic nature: how VFP developers view their future and what track they want to follow.

Saying Visual FreePro will die because of a lack of resource is a self-fulfilling prophecy.

Also based on my experience, and seeing many clients around us, while I believe that migration to another platform / technology is absolutely great, the best from a technological point of view, it's also very difficult, if not impossible to achieve from an economical stand point.

I see many companies (mainly SMB's) running entirely on VFP, for whom moving somewhere else would mean so many changes, so many inflection points, so many business risks that it requires a very strong engineering team to carry on safely. It also appears that many of these companies can't afford these engineering skills, for both economical and cultural reasons.

I hope some day there will be enough member in the community sharing this view, and at this time there will be enough energy and business necessity to build some common long-term view on how to continue run these businesses while building on the VFP legacy.