Craig,

I initially tried installing the DLL using the Component Services Manager. I had the same problem described below...so I deleted it from the Component Services Manager and registered the mtdll using REGSVR32. Still the same problem exists.

No I haven't tried calling the DLL from VFP before re-registering it. What is the purpose of trying it from VFP?

Joel

>This has nothing to do with COM+ unless you've installed the DLL as a COM+ application.
>
>When you try it on day 2, have you tried calling the DLL from VFP before you reregister it?
>
>
>>Windows 2000
>>VFP 8.0
>>
>>I have an Excel spreadsheet with a VBA macro that, using createobject() in the VBA macro, creates an object from my VFP mtdll and then passes cell references to the object. My VFP mtdll is registered using the following command:
>>
>>regsvr32 icitem.dll
>>
>>The mtdll looks up an inventory item number in a FoxPro for Windows free table called icitem.dbf and returns the item description.
>>
>>This all works wonderfully on the day the dll is registered. I can turn the computer off and back on again, login to the computer and the dll continues to work just fine -- but only on the same day that I register the dll. However, the next day when I come in and turn on the computer, the dll returns #VALUE to the spreadsheet cell that calls the dll methods. I know the dll is still being access from my Excel spreadsheet because when I enter an erroneous, blank item number (in the Excel cell), the dll returns an error message to the Excel cell, and I know the error message comes from my dll!
>>
>>Why does it work on the day I register it but not on subsequent days. If I unregister the dll, reboot the computer, re-register the dll, it works again. Can someone tell me what I'm doing wrong? Can someone perform a dll exorcism?
>>
>>Joel