Error 429 - ActiveX Component can't create object

[Bob Darlington]

I'm using Access 2002 to try to open Outlook 2002 (late binding) using:
Dim objOutlook As Object
Set objOutlook = CreateObject("O utlook.Applicat ion")

I get the above error if Outlook is closed when the routine runs.
If Outlook is open, it runs fine, but doesn't seem to open another copy of
Outlook (strange?)
It has been working OK previously, and the only change to my system (I can
think of) is the installation of Access 2003.
When I copy the program to another machine (with all the same apps
installed - ie A2002 and A2003 and OL2002) it works fine.

I've seen a couple of posts with similar problems, but can find no
solutions.
Any ideas appreciated.

--
Bob Darlington
Brisbane

[Tom van Stiphout]

On Fri, 10 Sep 2004 19:46:13 +1000, "Bob Darlington"
<bo*@dpcmanAX.c om.au> wrote:

Perhaps better to first call GetObject to see if an instance is
already running. Something like:
on error resume next
set o = GetObject(x)
if err.number<>0 then set o = CreateObject(x)
if err.number<>0 then Msgbox "Alarm - Outlook not installed?"

With late binding you may also be able to use IsObject to test if an
object was created.

-Tom.

I'm using Access 2002 to try to open Outlook 2002 (late binding) using:
Dim objOutlook As Object
Set objOutlook = CreateObject("O utlook.Applicat ion")

I get the above error if Outlook is closed when the routine runs.
If Outlook is open, it runs fine, but doesn't seem to open another copy of
Outlook (strange?)
It has been working OK previously, and the only change to my system (I can
think of) is the installation of Access 2003.
When I copy the program to another machine (with all the same apps
installed - ie A2002 and A2003 and OL2002) it works fine.

I've seen a couple of posts with similar problems, but can find no
solutions.
Any ideas appreciated.

[Bob Darlington]

Thanks for the reply Tom.
I tried your suggestion, but get the same result - Err 429 if Outlook is not
open before I start.

If Outlook is open, and I use CreateObject, it works fine.
If Outlook is open and I use GetObject I get err -2147221020 and it fails
IsObject returns true after CreateObject or GetObject.

CreateObject doesn't seem to open additional copies of Outlook as I would
have expected.
And I can't see why GetOject shouldn't work if Outlook is open.

As I said in my initial post, it all works fine on my notebook which is
similarly configured with WinXP, OfficeXP Developer and Access 2003.

Unless anyone has a better suggestion, I'll try uninstalling Access 2003
then, if that doesn't work, reinstalling Office XP.
--
Bob Darlington
Brisbane
"Tom van Stiphout" <no************ *@cox.net> wrote in message
news:i8******** *************** *********@4ax.c om...

On Fri, 10 Sep 2004 19:46:13 +1000, "Bob Darlington"
<bo*@dpcmanAX.c om.au> wrote:

Perhaps better to first call GetObject to see if an instance is
already running. Something like:
on error resume next
set o = GetObject(x)
if err.number<>0 then set o = CreateObject(x)
if err.number<>0 then Msgbox "Alarm - Outlook not installed?"

With late binding you may also be able to use IsObject to test if an
object was created.

-Tom.

I'm using Access 2002 to try to open Outlook 2002 (late binding) using:
Dim objOutlook As Object
Set objOutlook = CreateObject("O utlook.Applicat ion")

I get the above error if Outlook is closed when the routine runs.
If Outlook is open, it runs fine, but doesn't seem to open another copy ofOutlook (strange?)
It has been working OK previously, and the only change to my system (I canthink of) is the installation of Access 2003.
When I copy the program to another machine (with all the same apps
installed - ie A2002 and A2003 and OL2002) it works fine.

I've seen a couple of posts with similar problems, but can find no
solutions.
Any ideas appreciated.

[Tom van Stiphout]

On Mon, 13 Sep 2004 09:59:22 +1000, "Bob Darlington"
<bo*@dpcmanAX.c om.au> wrote:

I'm really surprised by this error -2147221020 = 800401e4 = Invalid
syntax.
Does this happen on other machines as well? A quick Google search
turned up mostly ADSI related issues - not much on Outlook. I think
your uninstall / reinstall is a good idea.

-Tom.

Thanks for the reply Tom.
I tried your suggestion, but get the same result - Err 429 if Outlook is not
open before I start.

If Outlook is open, and I use CreateObject, it works fine.
If Outlook is open and I use GetObject I get err -2147221020 and it fails
IsObject returns true after CreateObject or GetObject.

CreateObject doesn't seem to open additional copies of Outlook as I would
have expected.
And I can't see why GetOject shouldn't work if Outlook is open.

As I said in my initial post, it all works fine on my notebook which is
similarly configured with WinXP, OfficeXP Developer and Access 2003.

Unless anyone has a better suggestion, I'll try uninstalling Access 2003
then, if that doesn't work, reinstalling Office XP.

[Bob Darlington]

Thanks Tom
I saw a posting describing a similar problem, but no solution appeared in
the thread.
I'll do the reinstall later and post the result.

--
Bob Darlington
Brisbane
"Tom van Stiphout" <no************ *@cox.net> wrote in message
news:dn******** *************** *********@4ax.c om...

On Mon, 13 Sep 2004 09:59:22 +1000, "Bob Darlington"
<bo*@dpcmanAX.c om.au> wrote:

I'm really surprised by this error -2147221020 = 800401e4 = Invalid
syntax.
Does this happen on other machines as well? A quick Google search
turned up mostly ADSI related issues - not much on Outlook. I think
your uninstall / reinstall is a good idea.

-Tom.

Thanks for the reply Tom.
I tried your suggestion, but get the same result - Err 429 if Outlook is notopen before I start.

If Outlook is open, and I use CreateObject, it works fine.
If Outlook is open and I use GetObject I get err -2147221020 and it fails
IsObject returns true after CreateObject or GetObject.

CreateObject doesn't seem to open additional copies of Outlook as I would
have expected.
And I can't see why GetOject shouldn't work if Outlook is open.

As I said in my initial post, it all works fine on my notebook which is
similarly configured with WinXP, OfficeXP Developer and Access 2003.

Unless anyone has a better suggestion, I'll try uninstalling Access 2003
then, if that doesn't work, reinstalling Office XP.

[Bob Darlington]

To follow up my earlier posts, I have now uninstalled Access 2003 and Office
XP, then reinstalled Office XP and all SP's (up to SP3).
And it still won't work.
If anyone else has encountered this problem (with or without a solution) I
would like to hear about it.

--
Bob Darlington
Brisbane
"Bob Darlington" <bo*@dpcmanAX.c om.au> wrote in message
news:41******** **************@ news.optusnet.c om.au...

I'm using Access 2002 to try to open Outlook 2002 (late binding) using:
Dim objOutlook As Object
Set objOutlook = CreateObject("O utlook.Applicat ion")

I get the above error if Outlook is closed when the routine runs.
If Outlook is open, it runs fine, but doesn't seem to open another copy of
Outlook (strange?)
It has been working OK previously, and the only change to my system (I can
think of) is the installation of Access 2003.
When I copy the program to another machine (with all the same apps
installed - ie A2002 and A2003 and OL2002) it works fine.

I've seen a couple of posts with similar problems, but can find no
solutions.
Any ideas appreciated.

--
Bob Darlington
Brisbane

[Mike]

"Bob Darlington" <bo*@dpcmanAX.c om.au> wrote in
news:41******** **************@ news.optusnet.c om.au:

To follow up my earlier posts, I have now uninstalled Access 2003 and
Office XP, then reinstalled Office XP and all SP's (up to SP3).
And it still won't work.
If anyone else has encountered this problem (with or without a
solution) I would like to hear about it.

I found the following solution on Office Online. The problem is most
likely that for whatever reason, your DAO26.dll registry entries were
altered or removed. To re-register this control, click on Start | Run and
enter the following: regsvr32 "C:\Program Files\Common Files\Microsoft
Shared\DAO\DAO3 60.DLL". This solved the problem for me. Hope it works for
you.

[Bob Darlington]

Thanks Mike.
Tried it but didn't solve it.
--
Bob Darlington
Brisbane
"Mike" <mr*@mrc.mrc> wrote in message
news:Xn******** *************** @216.221.81.119 ...

"Bob Darlington" <bo*@dpcmanAX.c om.au> wrote in
news:41******** **************@ news.optusnet.c om.au:

To follow up my earlier posts, I have now uninstalled Access 2003 and
Office XP, then reinstalled Office XP and all SP's (up to SP3).
And it still won't work.
If anyone else has encountered this problem (with or without a
solution) I would like to hear about it.

I found the following solution on Office Online. The problem is most
likely that for whatever reason, your DAO26.dll registry entries were
altered or removed. To re-register this control, click on Start | Run and
enter the following: regsvr32 "C:\Program Files\Common Files\Microsoft
Shared\DAO\DAO3 60.DLL". This solved the problem for me. Hope it works

for you.