Hi gmayor,

Well, I have to give credit where credit is due!! How on earth were you able to research this certificate stuff and come up with a process to create a certificate then export it from a personal location and then import it to a trusted location. AND IT WORKED!!! I followed the steps as laid out and each step worked exactly as you indicated. Then I signed the original macro with the new trusted certificate and . . . it didn't work!! I tried it a few times and still got that "macro disabled" message. I stopped OL and restarted it and it still didn't work.

I was just about to post another message to you but tried it again by stopping and restarting OL, but this time I was asked if some things (modules or programs, I forget) should be trusted. They were all from MS and I think one of the locations was where the selfcert.exe came from. So I said they were trusted. I even got a similar message from Norton (I have Norton Security on my PC) and said that should be trusted. Then I tried the macro and it worked!!! I stopped OL and started it again and no longer was asked about the trusted stuff and the macro still works! Do you know why I wasn't asked about the trust stuff the first time I stopped OL and then restarted it. It took about 3 stops and starts for it to ask me about the trust stuff.

I didn't try the new version of the macro and will try that later. But at least the original macro now works when needed. I still can't get over how complicated MS made it for some one who might casually want to come up with a simple macro. I guarantee a normal user who might have some knowledge of VBA would have NO IDEA what to do with these certificates.

So thanks again for all your help!!!
Gerry