Access deleting Redemption dll (VBA 6.3, Outlook 2002/2003, Access 2000/20

Topic

New Reply

Hello to all. I’m hoping you can help me with a weird problem: Access is removing our Redemption dll.

One of our Access programmers references the Redemption dll in his code. He uses Redemption objects to send out emails to our users.

But often, we find that after running (or sometimes after just opening) his code, the Redemption dll has been deleted from the client workstation.

We download and register the dll on the client workstation, run the Access program, and again, the dll has vanished.

The code doesn’t contain any statements to delete the dll.

Has anyone seen this before? Any suggestions on what might be causing it?

Thanks in advance for your help.

Regards,

Bob

Reply | Quote

Replies

That sounds really bizarre! I don’t see how the DLL could be deleted by using it, and I cannot find any mention of this problem in Google (web or groups). I’d check and double check to make absolutely sure that there is no code that tries to install, update or delete Redemption.

Reply | Quote

I agree. I’m being asked to investigate it because (a) I’m the one who customized the Redemption dll for our firm and ( I’m the one who created the script that downloads and registers it on client machines. Neither of which should have anything to do with the file getting deleted!

I’ll refer the issue back to the programmer whose code seems to be associated with the problem.

Thanks for your input!

Reply | Quote

Maybe the interaction between Access and the DLL is triggering some security software. Are there any logs or quarantines you can check?

Reply | Quote

I’ve never heard of it. I’d try changing/checking the ermissions on the file to make sure no one else is deleting it.
Peter

Reply | Quote

Thanks but we’re positive it’s something happening during the running of the Access code.

Reply | Quote

Does “missing” mean missing from the PC entirely, missing from the references, or what? Are you using a sagekey script to install the runtime on each machine?

Reply | Quote

As I said in my original posting, the dll is deleted from the pc.

We install the dll via a VB program that downloads it from our network and then registers it. However, the problem also occurs when the dll is manualy downloaded and registered.

Reply | Quote

By the way, what version of Windows is involved, and what is the cut off version of Access in the subject line of the original post?

Reply | Quote

We don’t use sagescript to install.

We’re using Access 2000 with Windows XP Professional 2002 SP2.

Apparently the problem doesn’t happen when the Access code is run uncompiled. But when the compiled version is run, it happens every time, regardless of whether the user running it has full Access or only the run-time version.

Reply | Quote

That’s a very good point. I’ll pass it along to the programmer. Thank you!

Reply | Quote