>>>>Hello guys,
>>>>My question may sound silly, but where is the Win32api.dll
>>>>file located ?. I could not find it, even that I am able to
>>>>use it from within FoxPro, but when I tried to use it from
>>>>Visual Basic it can't find it. I made a search in my "C"
>>>>drive and it didn't show anywhere.
>>>>=This.Thanks("in advance")
>>>
>>>Luis,
>>>
>>>The term Win32 API is a bit ambiguous depending on your reference point. As far as Windows is concerned it refers to all the DLLs (and other files such as WINSPOOL.DRV) that Windows uses to run.
>>>
>>>As far as the FoxPro DECLARE DLL statement is concerned, including IN Win32API as the library tells VFP to search in KERNEL32.DLL, GDI32.DLL, USER32.DLL, MPR.DLL, and ADVAPI32.DLL for the function definition. This does not, however, include other files which are part of the API, such as the aforementioned WINSPOOL.DRV or SHELL32.DLL.
>> Thanks Guys !,
>>But, something else, to use the function that I need in Visual Basic I can't use
>>"Win32api", I have to use the the name of the DLL that holds the function
>>that I need, am I correct ?
>>Thanks again for your help.
>
>Luis,
>
>That's correct. VB requires the name of the actual DLL. If you do a Quick View of the files listed above, you'll find the names of the functions listed in a section with the heading: "Export Table". Note that in some cases, you'll ssee the letter "A" or "W" added. You can safely ignore this in the declaration.

If he's working in VB, why not just use the API Text Viewer that came with VB/VS to look at the proper declares - you can cut and paste the declarations right into VB code...