Problem with Outlook 2003

[Peter Adema]

Our IT department installed Outlook 2003 on my new laptop.
From that moment I cannon send mails via a macro in Access anymore.
It was working with Outlook 2000.
When I am in the Visual Basic screen and want to Debug, the next error
appears:
MS Access encountered a problem and has to be closed.
When I click on the details I see:
Appname:MSAccess.exe
Appver:90.0.3822 Modname VBe6.dll
Modver: 64.99.72 offset:0009792f

I presume I miss a dll file somewhere.
In the Visual Basic code I use this way of sending automatic E-mails in
Outlook.

Dim objolk As Outlook.Application
Dim objMailItem As Outlook.MailItem
Dim olkNameSpace
Dim signmail As String
Set objolk = New Outlook.Application
Set olkNameSpace = objolk.GetNamespace("MAPI")
Set objMailItem = objolk.CreateItem(olMailItem

 

[Tim Ferguson]

Our IT department installed Outlook 2003 on my new laptop.
From that moment I cannon send mails via a macro in Access anymore.

Either you have to have a digital ID certificate (can be expensive!) or you
drop the users' security level. Considering this is Outlook we are talking
about, I really would not recommend the second one!

Sorry.


Tim F

 

[Peter Adema]

Hello Tim,
Thanks for your anwer, but I do not really understand it.
How can there be a security issue if I only Debug an existing Visual Basic
routine in Access?
Are you sure the solution you gave is the right one?

Greetings Peter.

 

[Tim Ferguson]

Are you sure the solution you gave is the right one?

Actually, I realised it wasn't about one minute after I pressed the
<send> key... I went straight into the FAQ "I can't program Outlook any
more because of the security" and read the rest of your message later.
Sorry :-(


Back with your original message, I don't think I have very much to offer.
I would suspect a mdb corruption or a broken outlook installation, or
else a DLL-hell problem with mixed versions of Office. Try compacting &
repairing the mdb first; after that I can't help.


If you don't get any better answers here, you might try
m.p.outlook.interop or m.p.outlook.program_vba next.


All the best



Tim F

 

[Peter Adema]

I have found the problem myself.
I had a reference in VBA "Microsoft Activex database objects 2.1"
When I unchecked this option, the problem was solved.

 

[Tim Ferguson]

I had a reference in VBA "Microsoft Activex database objects 2.1"
When I unchecked this option, the problem was solved.

Sounds reasonable; well done.

All the best


Tim F