>I work in an office of just two programmers. My co-worker insists that we use Visual Pro-Matrix for all new applications. I have some class libraries that I have gathered up on my own from several different sources (such as Micro Endeavors, Inc.) that I like to use for building apps.
>
>Does anyone have any articles or other materials that would argue against using Frameworks like Visual Pro-Matrix? Or any amunition that I can use to argue against using Visual Pro-Matrix?
>
>Thanks for your help,
>Don Knoup
>dknoup@landal.com
>LanDal Software Solutions, Inc.

IMHO, I think frameworks are great. That being said, the only framework I'd use was one that had decent support including training. We're probably going to start using MaxFrame for all future apps. But this is at my current client. Future clients? Who knows.

The pro for using a framework is that it's standardized. The con for using a framework is that it's standardized. It really depends on what you're trying to do. If your libraries are extensive and you're very familiar with them and you can create apps quickly, maybe a framework isn't the best method, at least not for every app.

Look at each situation, if it appears to be very specific and requiring lots of little nuances that are specific to that client, chances are, a framework will create more work for you. On the other hand, if the app is *somewhat* generic in nature (generic is a bad word), a framework will probably save you time.

HTH

Matt