Glad to help. If you go to Amazon.com, you should be able to buy it for less than Microsoft's $109. Happy Programming and God Bless! Internet::WWW::CodeProject::bneacetp

thanks

Very easy, add #include "stdafx.h" to the files that give those errors. Make sure it's the first #include though.

It is possible. Take a look at this[^]. It's a project we are doing to make skinnable GUI components and controls for .NET and Win32. "Blessed are the peacemakers, for they shall be called sons of God." - Jesus "You must be the change you wish to see in the world." - Mahatma Gandhi

But what it was anyway? I'm curious lol Philip Patrick Web-site: www.stpworks.com "Two beer or not two beer?" Shakesbeer

I have fixed both problems. Thanks. I made my class all inline and that fixed my linker errors whatever they were. Case closed.

That's because preprocessors are stupid. When a preprocessor finds GetObject, it replaces it with GetObjectA or GetObjectW, depending whether you compile a Unicode version or not. Just put something like #undef GetObject after #include <windows.h> and everything should work fine.

Simpler way is to use ATLMFC. #include <atlstr.h> // CString support. String* strSomething; CString str = strSomething; But you will need to find a way to pack your ATLMFC7.0 redistributable when you release your app. Hope this helps.