MFC Static link vs MFC Shared DLL Issues

My program is behaving differently when I link with MFC statically vs. when I link with MFC as a shared DLL. (In both cases I an using a debug build, so this is not a debug/release issue.)

The first issue I noticed is with the CRectTracker. When I use a RectTracker while linking with a shared DLL everythink works correctly. The cursor changes when over the rect to a cross and the user can move the rect around the screen. But, when linking with with static MFC the rect tracker does not behave correctly. After the rect tracket is displayed, moving the cursor over the rect makes the cursor disapear. It does not change to the cross, it just disappears when over the tracking rect.

Any ideas what I can be doing wrong? Any ideas why this is and what I can do about it? Thanks!

Craig Smith

Your best bet would be to post a small sample project that displays this behavior. As it is, I'm not even sure where to begin guessing...

>Any ideas what I can be doing wrong? Any ideas why this is and what I can do about it? Thanks!

>Craig Smith
Hi Craig, you were doing nothing wrong. What happened is Microsoft acknowledged Bug
"BUG: BLOCKS32 Sample Fails to Show Cursors when Linked to MFC"
http://support.microsoft.com/kb/208856
Resolution:
Find and comment or delete a line in YourProject.rc file

#define _AFX_NO_TRACKER_RESOURCES

and all will work fine.
I have spend a week trying to find the reason :(. I regret that the post is very old and my answer will not be needed most probably :).

Good post in some way Sasha but these days most programmers have abandoned VS6 for something more compliant.

Wow, this thread died years ago, I'm surprised that anyone would post to it.