Hi Victor,

Here is a perfect example of a developer dividing into his framework "tribe" and blindly throwing spears at the other side. In a previous posting you have claimed about VPM:

"It doesnt even use the VFP DBC!"

and when I point out that you are wrong you change your criticism to:

"Ok it allows use of the DBC but uses its own extended stuff that you have to setup on yer own in order to get the form development side of it too work."

So, one minute you say VPM doesn't use the VFP DBC, the next minute (when challenged) you say it does - but now we are supposed to believe you that VPM uses it badly (when 24 hours ago you were telling everyone it didn't use it at all). Interesting ?!?

In another statement you claimed:

"Heck you can't even use Source Safe with it unless you blow more $ on some stupid program they sell you so you can."

Again when told that I use SourceSafe with VPM without any additional $ modules, you change the criticism to:

"Yes & I was able to acomplish this as well...of course promatrix likes you to use their project manager & not so much the VFP one so yeah you can get it to work...with a few extra steps EVERY time you want to checkin-checkout."

So, one minute you are claiming you can't use SourceSafe with VPM (without an additional $ module) and the next minute (when challenged) you say it does. Yet again, we are supposed to now believe you that it does it badly and requires extra steps every time. Not that I think you are listening but FYI you can open VFP without VPM or you can even open the project manager within VPM. There are no extra steps at all. There are exactly the same number of steps regardless of whether you are working with a VPM application as there are with a "pure, non-framework" VFP application.

I could pick holes in the other "faults" you have with VPM and your subsequent changes in response when challenged but I am not going to waste anyone's time as it will achieve nothing. If it is important to you that "your framework is better than mine" then I will agree to that if it makes you happy.

Constructive criticism should always be welcomed as nothing is perfect, however, false criticism simply to try and prove that your framework is better than someone elses is pointless. I would ask anyone following these posts to take a careful look over the original negative statements made here and how they have been twisted when challenged. Sadly, the only consistent feature is the need and desire to criticise VPM regardless of the claims.

At the end of the day I don't know whether VPM is equal, better or worse than any other framework. What I do know is I am more than happy with it and have no desire to look elsewhere. As a non VFE user if I ever choose to look at it in detail it would sadden me greatly if I let myself be sidetracked by some other framework's users throwing false accusations at it.

The risk in making sweeping statements is that if you are found out it can un-earth you as someone who simply wants to throw spears.

Aaron