google
"vfp declare dll winapi"
and you get enough examples of declare dll, look up the corresponding WinAPI declaration to get a feel for parameter syntax
structs need to be packed into vfp strings, AFAIR there was a vfpstruct by Christian Ehlscheid for tougher problems if you do not want go a C/fll route




>Thank you Naomi,the Russinovitch site is very usefull (many advanced tools)
>
>Process explorer can be found at https://technet.microsoft.com/en-us/sysinternals/bb896653
>its an advanced taskManager viewing all processes running on system with some fields.
>it can return for a running process what dll are used...
>Unfortunatly it cannot for a specific dll (it cannot load it) return the tree,the functions used,....
>
>i found the dependencyWalker downloadable at http://www.dependencywalker.com/
>from this site:
>Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module, and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more.
>
>i think its a start for my problem.