Re: Unicode support in OpenStreamOnFile? Is it a bug?
- From: "Stephen Griffin [MSFT]" <sgriffin@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 Jun 2008 09:37:50 -0400
The header is wrong - this function only takes CHAR*, never WCHAR*.
"Ashutosh" <smbs-msdn@xxxxxxxxxxxxx> wrote in message
news:ubQZwdnyIHA.5820@xxxxxxxxxxxxxxxxxxxxxxx
Hi, I have a doubt that this method/function has a bug. Can someone please
confirm.
HRESULT STDMETHODCALLTYPE OpenStreamOnFile(
LPALLOCATEBUFFER lpAllocateBuffer, LPFREEBUFFER lpFreeBuffer, ULONG
ulFlags, LPTSTR lpszFileName, LPTSTR lpszPrefix, LPSTREAM FAR *
lppStream);
This method/funciton takes LPTSTR as the file name. So, when unicode is
defined, it should take name as WCHAR, but it always returns file not
found error...However, with unicode defined and I pass char array, it
works..
I have tried passing MAPI_UNICODE flag also when passing WCHAR array.
So, is it a bug in OpenStreamOnFile ??
Thanks & Regards,
Ashutosh
.
- References:
- Unicode support in OpenStreamOnFile? Is it a bug?
- From: Ashutosh
- Unicode support in OpenStreamOnFile? Is it a bug?
- Prev by Date: Re: Problem opening a msg file using ShellExecute
- Next by Date: Re: SetSearchCriteria difficulties getting results
- Previous by thread: Re: Unicode support in OpenStreamOnFile? Is it a bug?
- Next by thread: SetSearchCriteria difficulties getting results
- Index(es):