>>Rick I beg to differ. FoxWeb is not a framework. It is a means of creating Web Applications using FoxPro code. It is very good at that and is supported/documented very well. But it is not a FrameWork package.
>> Just thought this needed a little clarification.
>
>It's a Web framework. Framework just means providing the tools to interface in this case, not necessarily an entire architecture. The goal of any of these tools is to let you use VFP in the most natural manner possible within a Web application. Well, at least that's my goal with Web Connection. The 'framework' should not get in the way of the language.
>
>I think all the tools have the basic connector features - they have to. Others build on top of that for more support and easier operation. As to FoxWeb I can't say I know much about it recently. All I can judge by is what I see of it these days in any public avenua which isn't much...

But when asking for a FrameWork most people look to things like http://fox.wikis.com/wc.dll?Wiki~FrameworkSalesMarketingInformation

So you see it is beginning to be a term that is confusing those who read and think they are buying a complete turn-key package. Which FoxWeb is not.