COM Add-IN and Access 2000 run-time

[Guest]

Hi all,

I created an Outlook 2000 COM-AddIn and in a test one user is getting the below error message at startup:

"The path 'Microsoft Access 2000 Runtime' cannot be found. Verify that you have access to this location and try again, or try to find the installation package 'data1.msi' in a folder from which you can install the product Microsoft Access 2000 Runtime."

What could be causing this error and how can I go about troubleshooting it (where to start looking)? What does Access 2000 have to do with this, it isn't referenced in any way in my add-in.

Any ideas anyone?

Thanks in advance,

Selgin

 

[Ken Slovak - [MVP - Outlook]]

The Access runtime is usually used if the code is calling Access
functions or using ADO and Access isn't installed. Does your code use
any ADO or other database type accesses? Does that user have MDAC
installed? If not that could possibly trigger that message. Did you
double-check your project references and any dependencies in merge
modules you included in your installation package?

Hi all,

I created an Outlook 2000 COM-AddIn and in a test one user is

getting the below error message at startup:

"The path 'Microsoft Access 2000 Runtime' cannot be found. Verify

that you have access to this location and try again, or try to find
the installation package 'data1.msi' in a folder from which you can
install the product Microsoft Access 2000 Runtime."

What could be causing this error and how can I go about

troubleshooting it (where to start looking)? What does Access 2000
have to do with this, it isn't referenced in any way in my add-in.

 

[Guest]

Thanks for the response Ken

No, my code doesn't access any database, which is why this is a Mystery to me. Would Outlook require MDAC even without such Access calls. The user does have MS Access installed as well

My installation package only includes the one dll file that makes up my COM-AddIn. Since users have Ofiice 2000 and Outlook 2000 installed, I assumed that any Office dependencies would already be installed on the machine. Or is this an incorrect assumption

In my code I'm not doing any database access or anything external to the Outlook Object model.

----- Ken Slovak - [MVP - Outlook] wrote: ----

The Access runtime is usually used if the code is calling Acces
functions or using ADO and Access isn't installed. Does your code us
any ADO or other database type accesses? Does that user have MDA
installed? If not that could possibly trigger that message. Did yo
double-check your project references and any dependencies in merg
modules you included in your installation package

-
Ken Slova
[MVP - Outlook
http://www.slovaktech.co
Author: Absolute Beginners Guide to Microsoft Office Outlook 200
Reminder Manager, Extended Reminders, Attachment Option
http://www.slovaktech.com/products.ht

Hi all

that you have access to this location and try again, or try to fin
the installation package 'data1.msi' in a folder from which you ca
install the product Microsoft Access 2000 Runtime.troubleshooting it (where to start looking)? What does Access 200
have to do with this, it isn't referenced in any way in my add-in

 

[Ken Slovak - [MVP - Outlook]]

Outlook doesn't require MDAC to be installed at all unless you are
trying to connect to Outlook using an ODBC connection. And installing
Access installs MDAC anyway.

You must reference the Outlook and Office libraries in your project
unless you are using late binding for everything (Object instead of
MailItem for example), but distributing any Outlook or Office
libraries isn't legal and is unnecessary.

So your installation package doesn't include any merge modules (MSM
files) or anything like that? No ActiveX controls (OCX's) or other
DLL's? What installer are you using, BTW?

This is one I've never heard of or seen before. Have you tried posting
on an Access programming group and seeing if any of the people there
have ever seen such a problem? Even if the direct causes are different
it might point you in the right direction.

Thanks for the response Ken.

No, my code doesn't access any database, which is why this is a

Mystery to me. Would Outlook require MDAC even without such Access
calls. The user does have MS Access installed as well.

My installation package only includes the one dll file that makes up

my COM-AddIn. Since users have Ofiice 2000 and Outlook 2000 installed,
I assumed that any Office dependencies would already be installed on
the machine. Or is this an incorrect assumption?

In my code I'm not doing any database access or anything external to

the Outlook Object model.

 

[Guest]

I used Visual Installer (Visual Studio 6.0) to compile the initial MSI file. Then used Orca to do some modifications so I can make upgrade packages. Also, there are no merge modules or activeX controls. Just the single dll file that is my COM Add-In.

I agree, this is a weird one, there is nothing in the code of my add-in to cause this. I think you may be onto something with what you mentioned about distributing Office and Outlook libraries with the Add-In. If this was to eliminate the problem, than what would that indicate

Thanks for your replies

Selgi

----- Ken Slovak - [MVP - Outlook] wrote: ----

Outlook doesn't require MDAC to be installed at all unless you ar
trying to connect to Outlook using an ODBC connection. And installin
Access installs MDAC anyway

You must reference the Outlook and Office libraries in your projec
unless you are using late binding for everything (Object instead o
MailItem for example), but distributing any Outlook or Offic
libraries isn't legal and is unnecessary

So your installation package doesn't include any merge modules (MS
files) or anything like that? No ActiveX controls (OCX's) or othe
DLL's? What installer are you using, BTW

This is one I've never heard of or seen before. Have you tried postin
on an Access programming group and seeing if any of the people ther
have ever seen such a problem? Even if the direct causes are differen
it might point you in the right direction

-
Ken Slova
[MVP - Outlook
http://www.slovaktech.co
Author: Absolute Beginners Guide to Microsoft Office Outlook 200
Reminder Manager, Extended Reminders, Attachment Option
http://www.slovaktech.com/products.ht

Thanks for the response Ken

Mystery to me. Would Outlook require MDAC even without such Acces
calls. The user does have MS Access installed as wellmy COM-AddIn. Since users have Ofiice 2000 and Outlook 2000 installed
I assumed that any Office dependencies would already be installed o
the machine. Or is this an incorrect assumptionthe Outlook Object model

 

[Ken Slovak - [MVP - Outlook]]

Well, since it's illegal to distribute those libraries and you'd also
have to distribute (illegally) any dependencies for those libraries I
can't say

If you can create an Outlook.Application object on those machines:
Set oOL = CreateObject("Outlook.Application")
Then Outlook is registered on those machines.

I used Visual Installer (Visual Studio 6.0) to compile the initial

MSI file. Then used Orca to do some modifications so I can make
upgrade packages. Also, there are no merge modules or activeX
controls. Just the single dll file that is my COM Add-In.

I agree, this is a weird one, there is nothing in the code of my

add-in to cause this. I think you may be onto something with what
you mentioned about distributing Office and Outlook libraries with the
Add-In. If this was to eliminate the problem, than what would that
indicate?

 

[Guest]

I meant to ask that question from a technical perspective and not a legal one ie. remebering that Outlook 2000 and Office 2000 are installed on the user's PC, if deploying these libraries did elminate the problem then what does that indicate (if anything, does it shed some light?).

Although you did answer this with somewhat with your CreateObject example below

Thanks again for your answers on this.
----- Ken Slovak - [MVP - Outlook] wrote: ----

Well, since it's illegal to distribute those libraries and you'd als
have to distribute (illegally) any dependencies for those libraries
can't say :

If you can create an Outlook.Application object on those machines
Set oOL = CreateObject("Outlook.Application"
Then Outlook is registered on those machines

-
Ken Slova
[MVP - Outlook
http://www.slovaktech.co
Author: Absolute Beginners Guide to Microsoft Office Outlook 200
Reminder Manager, Extended Reminders, Attachment Option
http://www.slovaktech.com/products.ht

I used Visual Installer (Visual Studio 6.0) to compile the initia

MSI file. Then used Orca to do some modifications so I can mak
upgrade packages. Also, there are no merge modules or active
controls. Just the single dll file that is my COM Add-Inadd-in to cause this. I think you may be onto something with wha
you mentioned about distributing Office and Outlook libraries with th
Add-In. If this was to eliminate the problem, than what would tha
indicate

 

[Ken Slovak - [MVP - Outlook]]

Well, if you have access to a machine where it doesn't work you can
run the Office Repair option either from Detect and Repair in the
Outlook Help menu or for Office in Add/Remove Programs and see if that
helps. That would rewrite all the registrations for Outlook and would
be something that would work better than trying to distribute some
libraries. The Outlook libraries are dependent on each other, so if
one or two were damaged or misregistered you'd almost have to
reinstall Outlook to fix things. The repair options would do that.

I meant to ask that question from a technical perspective and not a

legal one ie. remebering that Outlook 2000 and Office 2000 are
installed on the user's PC, if deploying these libraries did elminate
the problem then what does that indicate (if anything, does it shed
some light?).

 

[Guest]

This sounds worth trying, I don't have access to the machine in question but someone else will have a go at it. I'll follow up here and let you know if it worked when I receive news. Beyond that probably not much more to add.

Your posts have been helpful, thanks again.

----- Ken Slovak - [MVP - Outlook] wrote: -----

Well, if you have access to a machine where it doesn't work you can
run the Office Repair option either from Detect and Repair in the
Outlook Help menu or for Office in Add/Remove Programs and see if that
helps. That would rewrite all the registrations for Outlook and would
be something that would work better than trying to distribute some
libraries. The Outlook libraries are dependent on each other, so if
one or two were damaged or misregistered you'd almost have to
reinstall Outlook to fix things. The repair options would do that.