BTW-

We have this command to init foxtools.FLL, which of course calls DDEREG.EXE when we try to use D100.DLL :

SET LIBRARY TO C:\ipc\LIBS\foxtools.FLL ADDITIVE

>HI ALL.
>
>In our Fox5 application, we had DDEREG.EXE and a 3rd party 16bit-dll D100.DLL under c:\ipc\libs where we manage all of our libraries.
>
>We converted this app to Fox7,
>
>And now when we run the app it is looking for DDEREG.EXE and D100.DLL under C:\Program Files\Common Files\Microsoft Shared\VFP\
>
>it no longer recognizes them under c:\ipc\libs
>
>Is this a Fox7 thing? Or the way it was packaged? Or something else?
>OH, SO MANY THANK YOU'S FOR YOUR HELP!
>:)
>
>>In Foxtools.chm you can find few lines about this:
>>
>>Fll32_16.dll is used for calling 16-bit DLLs under win32s. It uses the universal thunk to call 16-bit DLLs.
>>
>>Ddereg.exe is used for calling 16-bit DLLs under win32. It uses DDE to call 16-bit DLLs.
>>
>>You can find usefull some functions in Foxtools.fll, which have no analogues in VFP 7, but some of them can be replaced with API calls:
>>
>>MkDir(), RmDir(), Words(), WordNum(), NextWord(), RGBComp()...
>>
>>THERE ARE SOME UNDOCUMENTED USEFULL FUNCTIONS ALSO.
>>
>>Nik