Brian Converse wrote in a message to Kevin Ring:

MB> My advice is to look at MFC as throwaway effort, worth only what
MB> you are  being paid to use it.  It is not an especially friendly 
MB> tool, it tends to be incompatible with itself from one  version to
MB> the next, and has a number of features which  simply do not work. 

 BC> It may be worth a bit more. There are more employers out there who
 BC> look for people with "MFC" on their resume than there are who look
 BC> for any other class library.

 BC> "Win 95 + VC++ & MFC" is the industry standard. Of
course, the fact
 BC> that these employers use such a narrow filter tells you reams about
 BC> what working there will be like.

This is understandable...  Though since I work for myself, I'm more
interested in the "best" solution rather than the "most
popular" solution.  OpenClass sounds like the way to go, but I'd
really hate to have to shell out another couple hundred bucks for another
compiler.  

I've been working with VC++ 4.0 and MFC for the most week or two, and must
admit it is quite easy to work with for the relatively simple stuff I'm
doing.  I only wish I could change a compiler option and get an OS/2
version. :)

Kevin 
---