office 2003 and office 2007

[bil_drk]

i have a computer with office 2003 installed on it, and recently i installed office 2007 on it. however, everytime i open access 2003 the "preparing to install" wizard opens, and has to configure office 2003. same happens when i open access 2007, the "preparing to install" wizard opens and then it has to configure office 2007. i recently had this experience with word, and managed to fix that, but i don't know how to fix this problem with access. thanks for your help.

[kpac]

See here: http://www.computerhope.com/forum/index.php/topic,76886.0.html

[bil_drk]

but will this work for access?

[Carbon Dudeoxide]

I have no conflict with my Access 03 and 07. Try adding those entries to the registry and see if it works.

[bil_drk]

i added these entries to the registry; it didn't fix the problem. can you have two versions of access of one computer?

[patio]

Yes.

[bil_drk]

can you tell me how to where they won't conflict with each other?

[bil_drk]

IS ANYONE GOING TO ASSIST ME? I COULD USE SOME HELP!

[BC_Programmer]

have you tried reinstalling both versions of Office/Access? Starting with the earlier version, 2003.

P.S your refund check can be made out to you at any time.

[bil_drk]

fine, make it out to.........
yes, i have tried uninstalling both applications and reinstalling them by the older version first, it still didn't help. i've read about a registry hack for word for this same problem, isn't there one for access?

[BC_Programmer]

I had similar issues with Office 2000 and 2003; but they were so similar that I simply uninstalled 2000...

anyway, I'd try using the word hack, which adds the NoReReg Value in:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Options

and changing that simply to:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Options

[bil_drk]

access 2007 does not have this key value. what should i do now?

[BC_Programmer]

your changing 2003, not 2007.

[bil_drk]

access 2003 doesn't have it either

[BC_Programmer]

add a DWORD value, noReReg, to the key:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Options

if the key and/or values don't exist create them.

[bil_drk]

i created the key "options" and isserted the DWORD value noReReg, but that still didn't cure it. what can i do now?

[BC_Programmer]

Well, I'm out of ideas.


Aside from the MSI installer popups do they work?

[bil_drk]

yeah. somewhat

[Carbon Dudeoxide]

Do you NEED both version of Access?

[BC_Programmer]

another good point- if the only thing that makes you retain Access 2003 is it's User Interface, I believe there are add-ons /modifications to the 2007 version that put the older UI from 2003 into 2007. (I know there is one for word/excel/powerpoint- I think it's an office-wide add-on)

[kpac]

another good point- if the only thing that makes you retain Access 2003 is it's User Interface, I believe there are add-ons /modifications to the 2007 version that put the older UI from 2003 into 2007. (I know there is one for word/excel/powerpoint- I think it's an office-wide add-on)

I don't think you need any "add-on". My Office 2007 is able to read all previous versions of Office files.

[BC_Programmer]

I don't think you need any "add-on". My Office 2007 is able to read all previous versions of Office files.

 

I believe there are add-ons /modifications to the 2007 version that put the older UI from 2003 into 2007

Either way Access is a special beast when it comes to file types since it isn't an "access" data base it opens but a Jet Database, whose format is determined entirely by the version of the installed JET database engine installed; Each version has a different Database engine version included with it.

However after installing Access 2007, if the DAO libraries are binary compatible with the previous versions (and I see no reason why not) then it's likely that Access 2003 will also create Databases using the newer engine, making them unreadable to a "pure" 2003 install.

This is where the re-registration comes in, assuming MS was unable to setup a side-by-side configuration for the two Access versions, the next best thing is to do what the OP is experiencing, which is the re-registration of the appropriate components.