CFileDialog generating Kernel32 error
I found the problem. Ironically it's something I dealt with earlier this
year and for the life of me it didn't trigger anything in my memory.
Thankfully a google search found the problem and solution. I've included it
below if anyone is interested. I'm using the #define _WIN32_WINNT 0x0500.
On Fri, 24 May 2002 09:05:43 -0700, "Stephen Fogarasi"
Quote:
>My
MFC based program, that uses some SDK routines was working fine with the
>August 2001 SDK release, but when we loaded (all of) the November 2001 SDK,
>we consistently get a crash during the destructor call in CFileDialog.
>This problem occurs on a number of machines, all variants with the
following
>configurations :
> Does anyone have similar problems, or better yet, a solution for me ?
the only real sulution (without recompiling the MFC) is change in
..\VC98\MFC\Include\AFXDLGS.H the OPENFILENAME to somthing like this:
#ifdef _WIN32_WINNT>0x0400
OPENFILENAME_NT4 m_ofn;
#else
OPENFILENAME m_ofn;
#endif
Quote:
> I have a weird one that I can't debug.
> I am using a CFileDialog in my application. The code has been in place
for
> a long time and has worked fine. I recently reinstalled my development
> machine from scratch and now the code which uses the CFileDialog crashes
> when the calling function edits and the CFileDialog goes out of scope. It
> doesn't matter if I do anything with the CFileDialog. If I just declare
it
> it'll crash when the function ends.
> It's giving me an error at 77e873bb in Kernel32.
> Any clue on how to track down what is different on my system and what's
> causing the error? My other developers don't get the error with builds
they
> create.
> Thanks
