Should you be able to create your own mfc42.dll from the MFC/SRC source files (plus whatever else is available to the VC++ developer)? I'd like to put some breakpoints in MFC code to debug a release-only problem. dahill

This problem looks similar to mine. Unfortunately, I don't understand this answer. When I change the 'signature' of my own OnInitDialog function to match your suggestion, it doesn't get called, even in DEBUG. Any more enlightenment to offer?:confused: dahill

Visual Studio 6 C++ says "cannot execute program" on my XP machine. The same Release .exe throws an exeption implicating ntdll.dll when launched outside of Visual Studio. Debug edition runs OK. Release edition runs OK on an NT machine. An intriguing database entry mentions a 'NO_NTDLL' option. Any experience with this? dahill

Based on a solution attributed to "melwyn" on http://www.codecomments.com/archive307-2004-3-160471.html I was able to get rid of LNK1209. I ended up using file version 6.0.8160.0 of MSPDB60.DLL in C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin. For some reason file version 6.20.9351.0 of mspdb60.dll cut from C:\Program Files\Microsoft Visual Studio\VC98\Bin brought the link error with it. -dahill

I have just found a similar LNK1209 problem posted in March, 2004 by "melwyn". Ominously, he didn't appear to get an answer (from the Message Board). -dahill -- modified at 17:36 Tuesday 28th February, 2006

Thanks for the input gentlemen- I have "rebuilt all" with no success. This link error reads, ".pdp differs from previous link; relink or rebuild" and (for me) only occurs in the DEBUG configuration. -dahill -- modified at 16:02 Tuesday 28th February, 2006

I get link error LNK1209 no matter how many times i retry. The .pdb file is there and updated. I've even tried replacing the LINK.EXE, DUMPBIN.EXE, EDITBIN.EXE and LIB.EXE files in the VC98 bin folder (I'm using Visual Studio 6). dahill