>Hi Cetin,
>I am using VFP 8. I looked at the error file and what I had listed in the first post was the extent of the error. I am inclined to agree with you, I believe the .dll is not needed and I am looking at taking it out. I did try putting in a DECLARE DLL statement and it did get rid of the error in the compile, but I am unsure what effect it will have on the code overall with .dll's used.
>thanks for your and everyone else's recommendations.
>Alp Berker

Alp,
It might cause errors at runtime when it's needed. It might be a possibility, in fact its declaration is in one of the files but the file is not added to the project. You might discover it like this (code references would be your friend here):

-Locate the code where it's called.
-Walk up in the hierarchy (what calls the procedure having that call line).
-If you happen to hit to 'main' w/o any declaration in between then it would be a surprise (maybe that procedure is never called from anywhere in application). If you can find the declare line then check if that file is in project.
PS: If you know the API declaration (and dll referenced) then your addition of declare yourself would just do. You might discover the declaration checking how it's called.
Cetin