Andy,

I'm not going to sell you VPM (although it is my preferred choice).
Unless you can let your customers wait for 2 years (the time to build your own framework) I would suggest to look at any framework available and use the one that suits your needs and/or financial room you have.
Also, when things change (and they do!) like client/server, n-tier, web-based and you bought a framework from a company who listens to the market and developers, THEY will create these additions to the framework, and you don't have to write them yourself. You can do the job you are good in, build apps for your customers, not continue to enhance the framework in order to be able to create the apps your customers need.

What Larry means is this:
There is no perfect framework (just like there is no perfect language) because there is always someone who likes another one better. That doesn't mean it is bad, just not your cup of tea.
And about those gotcha's, every framework has it's learning curve, you need to learn the way that framework works, just like you needed to learn how foxpro and visual foxpro works.
And about bugs, if there are bugs in a framework, the more the merrier.
If lots of developers use it, the change a bug is found are greater that that you are the only one who uses your own framework.
VPM has a great community, just like this one. On the promatrix newsgroups you will find lots of developers, helping others.

>So, you're saying that VPM may not be a perfect fit for everybody and that there are definately some "gatchas" to work out. Humm.... I gotta think about this a little bit. It all most sounds like I'd be better off creating my own frame work to work for me.

Regards,