"=?Utf-8?B?UGV0ZXIgQWRlbWE=?=" <PeterAdema@discussions.microsoft.com>
wrote in news:A0FE32D7-F932-4B41-907D-68E7E90D1642@microsoft.com:
> 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 - 02 Feb 2006 15:28 GMT
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.
> "=?Utf-8?B?UGV0ZXIgQWRlbWE=?=" <PeterAdema@discussions.microsoft.com>
> wrote in news:A0FE32D7-F932-4B41-907D-68E7E90D1642@microsoft.com:
[quoted text clipped - 17 lines]
>
> Tim F
Tim Ferguson - 02 Feb 2006 20:41 GMT
"=?Utf-8?B?UGV0ZXIgQWRlbWE=?=" <PeterAdema@discussions.microsoft.com> wrote
in news:6B0C6737-A062-4241-961B-451656C7D63A@microsoft.com:
> 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