Hi Terry,

>I've never done this, but i have had fun looking up 80004005 . So I suggest from ignorance, but:
>You might be able to trap a 'provider; error by implementing COMRETURNEORROR() in your DLL's error method. It loads up AERROR(). It may trigger an excel error handler (if excel has one). You do have it hitting the first time! When you get it done, please be sure to share:)

COMRETURNERROR() seems to require you to provide an error message. I'm not sure how that is supposed to work - the object is failing to instantiate second time around, but exactly the same code works first time around.


>Is oTest being instanced and released each cycle? After Set oTest=Nothing, is there a way to assure that oTest is really 'Nothing'. What happens if oTest instances once and is left open until all the "cName$/oTest.getref()" have completed. Curious if it crashes or allows multiple cName$ cycles when oTest is NOT set to 'Nothing'. Does the task window look any different (Excel vs VFP)?

I've checked in the debugger in Excel, and the oTest object isn't hanging around. That was my first thought, but it doesn't appear to be the case. I want to instance the object and release it when I've finished with it.

>Someone that knows this stuff may drop by and make it really simple! I'd be interested in seeing how it turns out.

This DLL will eventually be used in a web server. It's really annoying when you get an error but no meaningful error message. I've tried using the object in VB, but I get the same error. VFP can use the DLL with no problems.

Best.

Matt.