>Hi Erik
>
>Some of your statements about VMP are inaccurate.
>
>>>because it is not a business object-centered framework<<
>VMP doesn't force you to use business objects, but it doesn't prevent you either.
>

I didn't say it prevented you. But if you choose to use business objects, you have to fend for yourself. The fact that VMP does not RELY on business objects means that it is a trap for beginning developers who might later need to expose their processes in a public API (COM). It might have changed since I saw it last, but the documentation I had for VMP made only a passing reference to business objects. This means that anyone trying to learn OO concepts by using the framework is going to be led astray.

>>>and did not like the view/table mixture it recommended for DE forms<<
>The DE forms all support views as the "main alias" so mixing is not mandatory.

That's why I said 'recommended'. I am sure there are lots of ways around doing stuff by the VMP 'book'.


All of my observations regarding VMP are only opinion and should be taken as such- I give no pretense of being a third party framework 'expert'.