Error 427 activex component can´t create object

I convert an access 2003 project (adp) to access 2007.

I was working fine in my machine where I have installed access 2003 and
access 2007 full installation.

Then I installed the application (access 2007 - ade) in a machine where has
installed office 2003 full installation and access runtime 2007.

It looked to work well until I click a button that run a code that open
outlook and attach a file. When run this code, shows the following error

Error 427 activex component can´t create object.

The references are ok.

I'm very frustrate, I'm spending a lot off time and I can not fix this issue.

Any suggestions?

Thanks a lot
JCP

Sorry, the error is 429 and not 427

"Jose" wrote:

I convert an access 2003 project (adp) to access 2007.

I was working fine in my machine where I have installed access 2003 and
access 2007 full installation.

Then I installed the application (access 2007 - ade) in a machine where has
installed office 2003 full installation and access runtime 2007.

It looked to work well until I click a button that run a code that open
outlook and attach a file. When run this code, shows the following error

Error 427 activex component can´t create object.

The references are ok.

I'm very frustrate, I'm spending a lot off time and I can not fix this issue.

Any suggestions?

Thanks a lot
JCP

Jose wrote:

It looked to work well until I click a button that run a code that open
outlook and attach a file. When run this code, shows the following error

Error 427 activex component can´t create object.

The references are ok.

I suspect the references are not ok on that system. They likely have
a different version of Outlook installed than you do. I'd suggest
using 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.

This also is very useful when you don't know version of the external
application will reside on the target system. Or if your organization
is in the middle of moving from one version to another.

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/