Click here to Skip to main content
15,913,100 members

Comments by fredrick72 (Top 3 by date)

fredrick72 25-Nov-13 8:36am View    
I may have had that backwards. For clarity i looked it up and this is the answer i found.

LPTSTR returns A LPWSTR if UNICODE is defined, an LPSTR otherwise. For more information, see Windows Data Types for Strings.
This type is declared in WinNT.h as follows:
C++

#ifdef UNICODE
typedef LPWSTR LPTSTR;
#else
typedef LPSTR LPTSTR;
#endif

So this makes a bit more sense; however, implicit conversion of char to w_char should have resulted in compile error. C++ certainly makes things difficult with all of these character types and definitions.
fredrick72 25-Nov-13 7:50am View    
I believe you are correct. the confusing part is that fileName is 16 bit and ofn.lptstrFile should return 16 bit when multi-byte char set setting is used. So in that example this should have worked. I even verified that the _MBCS flag was being set in the command properly.
fredrick72 21-Nov-13 13:46pm View    
Nelek,

It could be but then it works for the previous two edit controls. I am pretty much stumped at this point.