Hi!
Your DLL is actually a Foxpro library (FLL). You should recompile it for another
Foxpro version with new versions of files Winapims.lib and Pro_ext.h
Replace these files in your C project or change their paths in project to "your_path_here\Vfp98\Api".

>We are migrating from VFP 5 to VFP 6 and have a C dll we want to keep, but it doesn't play.
>
>In VFP 5, we set up access to this dll's functions simply with:
>
> SET LIBRARY TO mq_tools.dll
>
>In VFP6, we recompiled it, and it seems that the SET LIBRARY function won't work anymore for this purpose. Has there been a change, a restriction, in how FoxPro must talk to custom dlls?
>
>When I use a DECLARE statement to declare up one of the functions in this dll, and then call the function, I get message "Cannot find entry point in the DLL". I made sure that the upper/lower case of the name is exactly the same both in the dll and in the DECLARE statement, but that was not the issue.
>
>We wonder if we just haven't compiled it correctly, and that is why the functions are not visible to FoxPro. I am not a C person at all, and our new manager who has worked with C is baffled also.
>
>Hoping to find a FoxPro guru who has dealt with this very problem.