Erwin,

I have declared it as an OLEPUBLIC and built the DLL, but the problem I am having is that the VB program is software package we are selling, so the buyer will be doing the installation. If I did it your way, wouldn't I have to be the one installing it?

So far what I have tried is:

1. I included the TLB for the DLL, Foxpro DLLs and Exes (painful process of trying to track down the dependency information for everything) in the VB package and deployment wizard. When I install this on my test machine, I still get errors when I try to access the part of the program calling the DLL.

2. I tried to create a FoxPro installation with a dummy exe. I have tried saying the DLL is an ActiveX object or COM object but when I go to install it, FoxPro tells me it can't register it.

So I guess I am kinda lost on how I should distribute the DLL. Anymore ideas? :)

Thanks