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 :D ). 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

This thread (http://www.access-programmers.co.uk/forums/showthread.php?t=62601) may give you an idea of how to manipulate references.

OK, thanks for the hints.

What I went and done was open and edit 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…

As long as your code isn't using some feature new to 10.0, you're fine referencing the older library.

Thanks for the tip Pat!