I created a new form an started from scratch as you suggested. This form blows up in the same manner as the original application did... An c0000005 error on VFP7.exe. Worse yet, if I call the Quit() function on the DLL itself, it goes poof even before I clear the dll...

Next I deceided that if the VB sample code works, I should create an OCX to do the work for me. Not my preferred way of doing things, but if it works...
I tested the OCX in the ActiveX Control Test Container (provided with MS Visual Studio) again no problems.

Next I incooperate the OCX into my VFP app. like so:

CObject.Init
myObject = CREATEOBJECT("ZorgNed.MyOCX")

CObject.Search
myObject.FindInterestingStuff(Customer)
...more cool myObject functions...
and once I'm done

CObject.Destroy
RELEASE myObject

Guess what?? It blows up!! I'm beginning to see a pattern. I can't think of anything else now than the DLL being screwed up...Maybe on the DllCanUnloadNow or something.

I've requested a new version and I'll keep you posted on the progress.
Thanks for the help so far