>Srdjan, I was one of those who jumped immediately with VFP3- actually I was on the beta and found enough bugs to be gifted a copy of VFP3. What fun! Also I believe I deployed one of the first if not the first-ever 32-bit Windows application, written in VFP3 and deployed onto Win95 as soon as it was released.
>
>I remember bugs like the Requery() memory leak that caused endless frustration, but we felt that VFP's improved data features were worth the immediate switch. FWIW we were also wooed by Borland at the end of 1994 inviting us to move to Delphi and by MS telling us that VB would be the way to go. We chose VFP because we believed that its data features were better than the available alternatives.
>
>By 1997 we'd "seen the writing on the wall" and made the decision to move to Java, which turned out to be a bad idea at that time- it was too immature. Then by 2002 we moved some work to NET. Last year we redid some web stuff using PHP. And we keep some VFP.
>
>I know that there are people who disagree with the VFP angle. Presumably that is because their circumstances are different, which is cool. The only viewpoint that would concern me is if people stick with VFP without bothering to check what else is going on. But maybe that's the smartest response of all -maybe people like that will cruise along avoiding all the angst and turn out OK in the end. ;-)

Or you check everything, only to realise that VFP is still safest peace of the ice to skate on, in a given situation.
I just never understood why some people are taking NET and VFP as something mutualy exclusive.
I am VFP down to the bones, but if I ever need more then joomla website, I will gladly adopt some web development tool (like ASP.NET) and STILL use VFP for heavy data lifting, apps behind firewals etc.


BTW Did you check
http://www.visualwebgui.com/

Did not exactly understand their pricing policy, but framework looks really interesting.

Cheers :)