Hi all,

I'm using a third party DLL in one of my classes.
The function Declare_Dll_Functions (called in Init) does what it says, e.g. it declares some Win32 API functions and the functions from the third party DLL.

Now I can use the functions quite happily. When I'm done I call a CLEAR DLLS in the Destroy function of my class and VFP comes crashing down on me with a "Fatal Error: C0000005"

The class is created (becomes an object) upon a cmdButton.Click like so:

LOCAL oClass

oClass = CREATEOBJECT('cClass')
oClass.Search(Customer.Number)

RELEASE oClass

As far as I can see, there are no references to the DLL anymore. Yet, one of the functions in the DLL starts a seperate executable which is still running afterwards (actually, you start off by calling a Initialise function which fires up the executable or connects to it when it is already running). I have some Visual Basic sample code which doesn't seem to mind this, so why should VFP?

Anyone any pointers for me?
Maybe a unimportant detail, the crash occurs when switching the focus from VFP to another application (not necessarily the above mentioned executable)

Removing the CLEAR DLLS seemed a good idea at first, but I found that when running my app, using the DLL, next closing the app and run the app again then call the Initialise function from the DLL also crashed VFP.

It must be some kind of unreferenced thingamabob. I'm sure the DLL is registered, having used regsrv32. It's resided in the system32 dir of my WinXP Professional. VFP version is 7 with SP1.

Any help is welcomed