This looks like an internal Win32 function (I could not find it on MSDN
and I know this is not a CVI function). Usually this happens when you
build an app using the Win32 api and end up linking against a function
that is present only in a later version of the OS. One way of ensuring
this does not occur is to specify a WINVER define when building the
app. For example, if you WINVER to be 0x500, the Windows header will
automatically include only those API that are supported on Win2k or
higher. The windows.h file that ships with CVI FDS defines WINVER as
0x400 (Windows NT or higher)
In your Windows header file, you might have WINVER defined as 0x501 or higher. You can see that at the top of that file.
Try building the app again, only this time, add a compiler define in
the CVI build options as /WINVER=0x500 (for compatibility with Win2k or
higher)
For more information about WINVER, see this
link.
I hope this helps
Bilal Durrani
NI