Office Object Library differs on NT

[bavjean]

Hello,

I have a database which I run as a front-end .mdb file with the User
Interface and queries, and the back-end .mdb file which contains all tables
with data. I am running Access 2000 on WinXP.

I am constantly making changes to the front-end, and when necessary I
instruct my clients to copy the latest version of the front_end to their
local machines.

One unfortunate PC is still living in the dark ages and is on Windows
NT(although it does have Access 2000). And the problem is:
When I copy a new version of the front-end .mdb file to the NT machine, I
always have to go and change the references in Visual Basic for this file.
The NT machine’s references indicate that the Microsoft Office Object Library
10.0 is not available, and then I manually have to go change it to Microsoft
Office Object Library 9.0.

Is there a way that I can avoid this? i.e. having to go and change the
references each time before the user uses the front-end, and a run-time error
occurs. It goes without saying that if the solution is to upgrade Windows or
re-install Office, I will consider the option of manually changing it every
time.

Thanks very much in advance.
Jean

 

[Brendan Reynolds]

a) Are you actually using any of the objects in the Office object library?
If not, just uncheck the reference.

b) You say the PC has Access 2000 installed, but does it have Office 2000?
It could be a stand-alone installation of Access 2000 on a system with
Office 97 installed. If Office 2000 is installed, re-installing Office might
help, otherwise, you will need to use late binding.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

 

[bavjean]

OK, thanks for the hints. It is not a stand-alone version of Access 2000,
since there is also Powerpoint, Excel etc. in 2000 version.

What I went and done was open the front-end .mdb file from the NT machine
(instead of copying it to the local drive). Then I added the MS Office Object
Library 9.0 to the list of References. So now Library 10.0 is not there
anymore, and whenever someone copies the .mdb file to their local machine, it
references Library 9.0.

Is there anything bad in what I have just done? It seems that whatever
Library 10.0 has that 9.0 does not have, my application code doesn’t need.
I hope I haven’t gone and set off a bomb now or something…

 

[Brendan Reynolds]

I'm still wondering whether you actually need to reference the Office object
library at all. If you're not sure, try removing the reference and then
compiling. If you don't get any compile errors, you probably don't need it.
If you're using Option Explicit and you don't get any compile errors, you
definitely don't need it.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.