Actually, that is not entirely true.

You can build a vfp DLL without having an OLEpublic in it if you do the following.

Modify Project test nowait
_vfp.ActiveProject.Build("Test.DLL",4)

DECLARE SomeFunction in Test.dll

The DLL compiles without error, and with attempt to register itself. Plus the Declare statement does not through any errors either when executed. Unfortunately any attempt to call the function raises the error "Cannot find entry point SomeFunction in the DLL".

So far, all in all, the procedure outlined above is useless. But I would truly like to be able to create standard Win32 DLLs out of VFP to be reusable parts of my application. So far, I have had to rely on APP type of modules. But DLLs would look more professional to knowledgeable client.


>COM DLLs need to be registered, standard Win32 DLLs (cannot be created in VFP) do not.
>
>>Do all DLLs have to be registered? Is that just part of what a dll is? Are there DLLs that can be used by VFP without being registered?
>>
>>Thanks for your help.
>>
>>Rodd