>We have an application which uses custom dll's registered through Regfn and RegFn32 calls into foxtools.fll depending on whether the environment is 16 bit or 32 bit.
>
>Everything works fine in WFW3.11, and in NT. However, when we are closing down the app in Windows 95, the now familiar message "VFP has performed an illegal operation..." pops up. This happens at the end of the calling program, after all objects and dll's have been cleared. (I have checked it, they are cleared).
>
>The code at this point reads "SET LIBRARY TO". Even if we remove this line, (the next line being "CLEAR ALL"), the same thing happens. It seems that when VFP is releasing FOXTOOLS.FLL in W95, something weird happens. However, if the code is compiled as an .app it seems to be fine!
>
>We are using VFP3.0. Grateful for any clues.
>
>Thanks

Sanjay,

Unfortunately, I don't have any experience with Foxtools under VFP 3.0. The only thing that I could suggest would be to use conditional compilation to use the DECLARE syntax for the DLL calls under 32 bit Windows. For 16 bit, of course, you'd still have to use RegFN().

BTW, RegFN32() always makes calls to 32 bit DLLs (according to the documentation). RegFN() is dependent on the OS (16 bit DLLs under Win 3.1x, 32 under NT 3.51, 4.0 and Win 95).