Hi Jess,

> First I am absolutely not against third party frameworks

Then why is it that virtually every time someone specifically asks about them you respond with, "write your own?"

> And I salute him for that because he will not certainly be dependent on another company aside from MS on the long term basis. Unlike some who are becoming dependent to two or three instead of MS alone that is if they decided to be a plain user of the framework only, and not studying the architecture behind.

Actually, he's decided to rewrite the entire application in our VFP 6.0 version anyway. He's not comfortable with a hodge podge of all of the frameworks and since he wants to do three tier, ours was the most logical choice.

> How many guys out there who are becoming problematic on whom to ask if the error is of the Framework or on the VFP language?

The same issues exist with the VFP framework, except there's hardly any documentation and realistically no support. At any rate, all of the third party frameworks include source and are well supported.

> Frameworks are good but if a developer wanted to benefit even on the long term basis, he/she should study the architecture behind, otherwise, it is another unstoppable bucks of money will come out of his/her pocket for the next versions.

Of course anyone that uses any framework should study the architechture, however, that certainly doesn't mean they shouldn't upgrade. The cost of any of the VFP frameworks and the price of upgrades is easily offset by the cost of man hours to develop even a fraction of the features.