Re:Re: Has anyone seen this error come up for them ?
Yahia,
I'm running under Windows XP, this shouldn't be a problem.
Dean,
I'm not using any of those functions. The function is lstrcpynW and it's
exported by Kernel32.dll ( as I discovered via PEExplorer ).
My application is a COM application and the I've got several plugin type
components that interact with the base application via a defined COM
interface.
My guess is that something under the covers isn't being linked in correctly.
Yet, as I stated before, I have exactly the same code on both machine with
the compilers on each of those machines configured exactly
the same ( down to the directory structures and paths ).
My guess is that something either isn't linking right, or that the de{*word*81}
isn't working correctly within XP.
"Marcelo R. Lopez, Jr." <
XXXX@XXXXX.COM >wrote in message
Quote
Appl.exe - Entry Point Not Found
"The procedure entry point lstrcpynW could not be located in the dynamic
link library KERNEL32.dll".
My application is an application that encapsulates several COM-enabled
"plugins". I know I don't use lstrcpynW( or lstrcpynA ) directly, so I
started to poke around the header files to see what, if anything overtly
might point at it. I found in utilcls.h a template class called TCharBuff.
Even though I don't use it directly, does anyone know what parts of
ATL/VCL
support inside of Builder, might be using this template class, and what I
might be missing that won't resolve "lstrcpynW" correctly ?
Thanks to all in advance for any help they can supply.
Marcelo R. Lopez, Jr.
{smallsort}