Well,

After setting the Project hooks into Visual ProMatrix (VPME) and setting up the ProMatrix Source Control Kit (SourceSafe Integration). Establishing our development environment with SourceSafe and finishing the process of Subclassing the Frameworks Class Library structure into our own business classes/units (for those not using the three way class structure for VPME developed by ProSysPlus.Com) ---

Then adding to the huge flexibility that VPME Form Class Framework provides by subclassing into our own Form classes ---

Setting up and configuring the Activex integration hooks provided by VPME to support 3rd party products, establishing the VPME client installation environments required by these tools ---

Then setting up our Developers Menu provided as a buisness hook by the VPME framework (I hang a bunch of stuff here for RAD) ---

Wait, a bunch of VPME developers are now utilizing the xCase integration provided by xCase2VPM (www.prosysplus.com) and developing the ER diagrams outside the framework for total and seemless integration into the framework, and now having done that (and leaving out the advanced stuff for brevity's sake) ---

Well yah, I guess VPME is just for beginners <vbg>...

Cheers,


John C. Gunvaldson, CNE, MCP
ProMatrix MVP 2000, 2001
(xBase developer since 1985)


>>>>> Cecil wrote
I am beginning to think that ProMatrix is for developers who don't know much about Visual FoxPro and may need a crutch to get through its steep learning curve. Am I wrong?
>
>Cecil

(for the record Cecil, yes - If I may be allowed to say so, I believe you are way off. Why didn't you just ask us who use VPME? I've seen your posts before? All of us go out of our way to answer tons of VFP and VPME questions all of the time?)