I've been searching for an answer to this problem and I think I have it. Dungeon Craft doesn't use the MFC DLL's at runtime, it links all of that MFC code into the DC executables so there won't be any DLL dependency problems on the user's computer. I found this note on the Microsoft web page for the Learning Edition of Visual Studio:
"This means that, if you write programs that use the MFC library, the resulting executable will require that the MFC library code be available as a shared library (DLL). In other words, calls to the MFC library that you place in your code are resolved at runtime and not at link time. The MFC shared DLLs have names of the form MFC*.DLL."
So it looks like the Learning Edition does not come with all of the files that Dungeon Craft needs to link with.
Is there a work around? Probably yes. There are two ways to build DC. A release build and a debug build. The release build is the one used in the installer and it avoids using DLLs as mentioned above, but the debug build does use DLL's. You should be able to go to each of the three projects in Visual Studio, CDX, UAFWin, and UAFWinEd, and use the 'Set Active Configuration...' option to select Debug for CDX and select either 'Win32 Debug RT' or 'Win32 Debug PS' for UAFWin and UAFWinEd. Then rebuild all projects, CDX first.
[ 11-18-2001: Message edited by: CocoaSpud ]