VBLady
Member
My development partner is trying to use an ActiveX dll that I wrote in some ASP.Net code. Everything is relatively going well except one snag. If he uses the dll to access the target application hosted with dBase files, then tries to access the same files with ADO.Net, the files are locked out. The ActiveX DLL does not hold any of these tables open, and doesnt even access them directly -- but via the applications own API, and all of that clean up is done in the ActiveX DLL. His speculation is that this is happening because the ActiveX DLLs main object is not getting destroyed. He thinks I have to implement some sort of function in the ActiveX DLL to have it destroy itself because apparently you cant set an object = Nothing in ASP.Net. If this is incorrect, please let me know, and if it is correct, give me some guidance as to what I need to do in the ActiveX DLL. And how could I even have my dll destroy itself -- you cant call End in an ActiveX DLL.
Thanks for any insight on this,
Frances
Thanks for any insight on this,
Frances