access 2003 and 2007 being happy together

[Ian Burton]

Hi,
I hope this isn't a stupid question. This is something I solved for myself
a year or so ago when I got vista on my laptop, and I can't remember the
solution.
I have installed office 2003 on my machine, and then installed office 2007.
Although both versions are nominally there, and all works fine, apart from
Microsoft access, I can only easily work on access 2007 databases.

What seems to happen, is that even if I create a new db in 2003, when I look
at the references, it shows Microsoft Access 12.0 object library. I guess
this is the access 2007 reference, and so any queries fail on paramemters
and code etc. When I try and add the reference to the version 11.0
msacc.olb, it just does nothing, and so I wonder if anyone can help me. I
want to keep a database in access 2003

If anyone knows of what to do to fix this, I would be grateful. I am trying
to work on a very temperamental database, and I want to avoid the situation
of working on it in 2007, then going to another machine and resetting the
references and giving back to the client.

Thanks in advance.
Ian
P.S. my client machine is actually windows server 2008.

 

[Maurice]

Hi Ian,

Not a stupid question at all.
Although i'm not a 'fan' of installing two versions of access and so i
didn't I have to suggest something not tested.

Try setting your settings for 2007 to create databases in the 2000-2003
fileformat maybe that helps setting the reference option.

Settings under Office button-Access options - popular - default file format.
Give it a try...

 

[Ian Burton]

Maurice,
Thanks for your suggestion. I tried that, and then created a 2003 database
in 2007. However in references when I create a module, it still says
Microsoft Access 12.0 object library.

All very odd. I guess if someone else had both versions running side by
side, then they could verify it. I vaguely remember that the solution
originally was something to do with vista security, but I just can't quite
remember what it was.
Thanks,
Ian
,

 

[Rick Brandt]

Maurice,
Thanks for your suggestion. I tried that, and then created a 2003
database in 2007. However in references when I create a module, it
still says Microsoft Access 12.0 object library.

All very odd. I guess if someone else had both versions running side
by side, then they could verify it. I vaguely remember that the
solution originally was something to do with vista security, but I
just can't quite remember what it was.
Thanks,

You will see the reference to the Access object library of whatever version
of Access you are currently using. Nothing at all to do with the version
that the file is created in.

If I create a file in 2000 I will see the Access 9 library. If I open that
same file in 2002 I will see the Access 10 library, etc.. If you are
opening an Access 2003 file with Access 2007 (regardless of which version
you used to create it) you will see the Access 12 library.

Your original post suggested that you were opening the file with 2003 and
seeing the Access 12 library. THAT does sound wrong, but now I wonder if
you wrote what you actually intended to.

If you think about it the library being referenced HAS to be the one you are
currently running because for most people that is the only Access library on
their PC.

 

[steve_martin_athome]

You will see the reference to the Access object library of whatever version
of Access you are currently using.  Nothing at all to do with the version
that the file is created in.

If I create a file in 2000 I will see the Access 9 library.  If I open that
same file in 2002 I will see the Access 10 library, etc..  If you are
opening an Access 2003 file with Access 2007 (regardless of which version
you used to create it) you will see the Access 12 library.

Your original post suggested that you were opening the file with 2003 and
seeing the Access 12 library.  THAT does sound wrong, but now I wonder if
you wrote what you actually intended to.

If you think about it the library being referenced HAS to be the one you are
currently running because for most people that is the only Access library on
their PC.

Folks - I'm here to confirm what Ian is saying - haven't found a
solution yet but it certainly looks like a problem.
I've got 2002, 2003 and 2007 installed and I'm opening my original
2002 mdb with MSAccess 2002 yet now I'm getting similar funny VBA
error messages that we're there before (e.g. . If I look at the
references then I see even though I've opened MSAccess 2002 it's
referencing the Ms Access 12.0 Object Library" - what's better yet is
that I can't switch the reference back to v11 or v10 since it says the
reference is in use. Selecting the OLB from an earlier version just
gets ignored.

Opening a blank mdb in 2002 still references the latest v12 OLB.

Not sure if I've got all the service pack(s) for 2007 installed yet
but I'm likely to uninstall 2007 and re-install the older version for
now.