Microsoft Off 11/Off 9 Reference

[Dean]

I wrote a simple App in Access 2003 but used the 2000 file format. The
one module Requires reference to Microsoft Office 11.0 Object Library.
However, the person I have the code to has Office 2003 but only
Microsoft Office 9.0 Object Library.

Are they not backward compatible? Is there something the user can do
to update this to Office 11?

[Allen Browne]

You must use the correct library for the particular version of Access you
use. Access 2000 is Office 9. Access 2003 is Office 11.

The usual workaround is to use late binding. That is, omit the Office
reference all together, and declare the affected variables as simply Object
rather than as a specific type.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Dean" <de**@coveyaccounting.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...

I wrote a simple App in Access 2003 but used the 2000 file format. The
one module Requires reference to Microsoft Office 11.0 Object Library.
However, the person I have the code to has Office 2003 but only
Microsoft Office 9.0 Object Library.

Are they not backward compatible? Is there something the user can do
to update this to Office 11?

[Lyle Fairfield]

Dean wrote:

However, the person I have the code to has Office 2003 but only
Microsoft Office 9.0 Object Library.

Could this be?

[Wayne Morgan]

If the person has Office 2003 installed but no Office 11 Reference
available, then I would suspect a problem with the install. Since the Office
9 library is available, do they have both versions of Office installed? This
is possible to do, if done correctly.

--
Wayne Morgan
MS Access MVP
"Dean" <de**@coveyaccounting.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...

I wrote a simple App in Access 2003 but used the 2000 file format. The
one module Requires reference to Microsoft Office 11.0 Object Library.
However, the person I have the code to has Office 2003 but only
Microsoft Office 9.0 Object Library.

Are they not backward compatible? Is there something the user can do
to update this to Office 11?

[Wayne Morgan]

PS.

You say that they have the Office 9 library, the checked items at the top a
listed in preference order. In other words, Access will use these in the
order they're listed, hence the up and down buttons to the right of the
dialog. The unchecked references are listed in alphabetical order. Scroll
down the list to verify that the new library isn't there. If it is there,
you may have to uncheck the older one before it'll let you check the newer
one.

--
Wayne Morgan
MS Access MVP
"Dean" <de**@coveyaccounting.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...

I wrote a simple App in Access 2003 but used the 2000 file format. The
one module Requires reference to Microsoft Office 11.0 Object Library.
However, the person I have the code to has Office 2003 but only
Microsoft Office 9.0 Object Library.

Are they not backward compatible? Is there something the user can do
to update this to Office 11?

[David W. Fenton]

"Dean" <de**@coveyaccounting.com> wrote in
news:11*********************@o13g2000cwo.googlegro ups.com:

I wrote a simple App in Access 2003 but used the 2000 file format.
The one module Requires reference to Microsoft Office 11.0 Object
Library. However, the person I have the code to has Office 2003
but only Microsoft Office 9.0 Object Library.

Are they not backward compatible? Is there something the user can
do to update this to Office 11?

It may not matter. So far as I know, the Office object library is
unnecessary unless you use something in your code that is provided
by it (I've never found any need to do so), so you could try
removing the reference entirely and seeing if your code compiles.

I've seen the Office reference added in many times in my projects
and since I know for a fact that I never use anything from it, I
always simply remove the reference entirely.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Dean]

The object does matter as I am using a file dialog and a folder dialog
code.

I may follow Allen's advice on this. Something like
http://www.mvps.org/access/api/api0001.htm may work nicely.

[Douglas J. Steele]

The code in http://www.mvps.org/access/api/api0001.htm (and
http://www.mvps.org/access/api/api0002.htm for the folder dialog) is
definitely going to be less problematic from a distribution point of view.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"Dean" <de**@coveyaccounting.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...

The object does matter as I am using a file dialog and a folder dialog
code.

I may follow Allen's advice on this. Something like
http://www.mvps.org/access/api/api0001.htm may work nicely.

[Randy Harris]

"Dean" <de**@coveyaccounting.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...

The object does matter as I am using a file dialog and a folder dialog
code.

I may follow Allen's advice on this. Something like
http://www.mvps.org/access/api/api0001.htm may work nicely.

IMO - this is definitely the way to go if the application might be used by
multiple users. I had nightmares trying to keep track of which users had
which version of Office installed. There was no end to compatibility errors.
Code like that put an end to all of it. Permanently.

The code was written by Ken Getz, one of the authors of the Access
Developers Handbook (all versions). If you happen to have one of those, it
is on the included CD. The book has examples for using it.

Randy Harris

[David W. Fenton]

"Dean" <de**@coveyaccounting.com> wrote in
news:11**********************@g44g2000cwa.googlegr oups.com:

The object does matter as I am using a file dialog and a folder
dialog code.
Well, I would never do that. I always use the ADH code that directly
invokes the relevant APIs. From what I can tell, the code is not a
whole lot simpler, so I don't quite see why anyone would introduce
an outside dependency for something that can be done easily with
APIs.
I may follow Allen's advice on this. Something like
http://www.mvps.org/access/api/api0001.htm may work nicely.

That's basically the code that I've used, though from a later
edition of the ADH.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc