"Peter Caine" <(E-Mail Removed)> wrote:
>When executing the following VBA code, the program aborts
>on an internal error with an automation error code
> -2113732605(82030003).
>
>' Problem line
>Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
>
>The program works fine on a workstation running NT
>workstation and fails on a workstation running Windows
>2000.
Do they have different versions of Outlook installed? And you have a
reference that's missing on the system which fails?
If so once the code is debugged used Late Binding. Late binding means
you can safely remove the reference and only have an error when the
app executes lines of code in question. Rather than erroring out
while starting up the app and not allowing the users in the app at
all. Or when hitting a mid, left or trim function call.
You'll want to install the reference if you are programming or
debugging and want to use the object intellisense stuff. Then once
its running smoothly remove the reference and setup the late binding
statements.
Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")
For more information including additional text and some detailed links
see my Tips page on this topic.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm