Running Access 2007 and 2010 concurrently on a Windows 7 Pro computer
Have a client who has a mixture of XP and Windows 7 platforms, and is running Office 2007 on the XP boxes and 2010 on the Win 7 boxes.
I went out and bought a Win 7 laptop today, and am wondering whether others have had a problem running
Access 2007 and 2010 on the same box.
Don't know anything about virtualization, but understand that is one way to go. However, if the only problems are similar to running 2003 and 2007 on the same box, I'll just install both.
I went out and bought a Win 7 laptop today, and am wondering whether others have had a problem running
Access 2007 and 2010 on the same box.
Don't know anything about virtualization, but understand that is one way to go. However, if the only problems are similar to running 2003 and 2007 on the same box, I'll just install both.
"each time you switch from one version to the other."
IE ... the first time you open a db say in A2010 ... and you have been working in A2007 (different db) ... and vice-versa ... you will get that message.
mx
IE ... the first time you open a db say in A2010 ... and you have been working in A2007 (different db) ... and vice-versa ... you will get that message.
mx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Access 2007 and 2010 are *supposed* to be the same format, but I have seen problems both in opening an Access 2010 database in 2007 (Microsoft actually has produced a KB article on this problem, though it's not very helpful), and in opening 2007 databases in 2010. See my Access Archon #205 for a discussion of the first compatibility problem; there will be a note on the other problem in the Access Watch that contains Access Archon #206 (upcoming).
http://www.helenfeddema.com/Files/accarch205.zip
I recommend running each version in its own VM to avoid problems.
http://www.helenfeddema.com/Files/accarch205.zip
I recommend running each version in its own VM to avoid problems.
I gotta go with @mx on this. I have too many problems with objects like forms created in Acess 2007/2010 becoming corrupt when edited in Access 2003.
Still, I can see with the foolish Ribbon why you'd need 2003 and 2007/2010 together.
I'd REALLY throw some old box in a closet someplace and RDP into it to run Access 2007, if finalizing code and fixing busted references before deploying code is the only reason to do so.
I tried to run 2003/2007 with one in virtual machine for 4 months before giving up. 2007 was just far too destructive to my productivity. The constant corruption of objects created with the wizard when edited down-level made the gains from the wizard pointless.
YMMV
But really, stick an old box in a corner someplace, and rdp into it.
RemoteApps on a Server 2008 box is another nice option
Still, I can see with the foolish Ribbon why you'd need 2003 and 2007/2010 together.
I'd REALLY throw some old box in a closet someplace and RDP into it to run Access 2007, if finalizing code and fixing busted references before deploying code is the only reason to do so.
I tried to run 2003/2007 with one in virtual machine for 4 months before giving up. 2007 was just far too destructive to my productivity. The constant corruption of objects created with the wizard when edited down-level made the gains from the wizard pointless.
YMMV
But really, stick an old box in a corner someplace, and rdp into it.
RemoteApps on a Server 2008 box is another nice option
ASKER
Nick,
I'm running 2002, 2003, and 2007 on my desktop, and other than the "Please wait while Windows configure Office 20XX ..." annoying message I've not had any problems, although that my be because I almost never use a wizard.
My question is about installing both 2007 and 2010 on my new 64bit, Win 7 laptop. The only problem we have had so far is that some of the API calls don't work prpperly without a couple of modifications, and a conditional compilation variable. So what I have been doing is shipping them the Office 2007 (x86) version of the app and having their IT guy install it on the appropriate systems. He then saves the app with a "_64" added to the file name, changes the conditional compilation variable, saves the changes, and installs that version on the appropriate computers. Unfortunately, this means I'm sending him accdb files instead of accde files, and I need the ability to do that.
I would like to have 2007 and 2010 both installed on the laptop, got 2007 installed yesterday, but have not downloaded the XP virtual machine mentioned by KCTS yet. My goal is to continue developing in 2007 to meet that need, but then to open the file, change the conditional compilation variable and compile in 2010 for those machines. Anybody see a problem with this plan?
I'm running 2002, 2003, and 2007 on my desktop, and other than the "Please wait while Windows configure Office 20XX ..." annoying message I've not had any problems, although that my be because I almost never use a wizard.
My question is about installing both 2007 and 2010 on my new 64bit, Win 7 laptop. The only problem we have had so far is that some of the API calls don't work prpperly without a couple of modifications, and a conditional compilation variable. So what I have been doing is shipping them the Office 2007 (x86) version of the app and having their IT guy install it on the appropriate systems. He then saves the app with a "_64" added to the file name, changes the conditional compilation variable, saves the changes, and installs that version on the appropriate computers. Unfortunately, this means I'm sending him accdb files instead of accde files, and I need the ability to do that.
I would like to have 2007 and 2010 both installed on the laptop, got 2007 installed yesterday, but have not downloaded the XP virtual machine mentioned by KCTS yet. My goal is to continue developing in 2007 to meet that need, but then to open the file, change the conditional compilation variable and compile in 2010 for those machines. Anybody see a problem with this plan?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
HiTech - So how do I configure #2 and #3 above?
Strangely, when I installed 2007 yesterday, it appears to have automatically installed the 32 bit version, as Office did not show up in my program program list when I mouse over the Windows icon in the bottom taskbar at the bottom of the screen.
Strangely, when I installed 2007 yesterday, it appears to have automatically installed the 32 bit version, as Office did not show up in my program program list when I mouse over the Windows icon in the bottom taskbar at the bottom of the screen.
<I never touch the source mdb with 2007 or 2010>
It was this that was the killer to ALWAYS remember. I use a whack of references, and the minute you opened stuff up-level, the references silently update from 11.0 to 12.0 or 14.0. There is the IsBroken property for references, but you can't touch, remove or fix a broken reference. I even did paid support the MS on that. Can't be done. So you'd have to STOP STOP STOP STOP and eventually HALT, and then fix the references. EVERY single form or report that I have ever created with a 2007/2010 wizard and then proceeed to make significant alterations to in 2003 eventually results in
"There is not enough memory available to complete the requested operation"
The object is hopeless corrupted and has to be imported from another copy or recreated.
Since 2003 is the production version, I don't do any developing in 2007/2010 unless its for use only on those versions. My laptop runs 2010 and my desktop 2003.
RDP gets me what I need.
<then to open the file, change the conditional compilation variable and compile in 2010 for those machines>
Sounds like it could do so for you too, but OTOH you are well-versed in multi-version installation.
<automatically installed the 32 bit version>
Unless you nav'ed to the x64 folder and ran setup or downloaded the 64 bit Office then 32 bit is what installs.
The 64 bit version is still a little rough
http://www.pcworld.com/article/197415/beware_of_office_2010s_64bit_shortcomings.html
I know there's a whack of code changes that have to be made in moving to 64 bit VBA
http://msdn.microsoft.com/en-us/library/ee691831.aspx
That's my two bits :)
It was this that was the killer to ALWAYS remember. I use a whack of references, and the minute you opened stuff up-level, the references silently update from 11.0 to 12.0 or 14.0. There is the IsBroken property for references, but you can't touch, remove or fix a broken reference. I even did paid support the MS on that. Can't be done. So you'd have to STOP STOP STOP STOP and eventually HALT, and then fix the references. EVERY single form or report that I have ever created with a 2007/2010 wizard and then proceeed to make significant alterations to in 2003 eventually results in
"There is not enough memory available to complete the requested operation"
The object is hopeless corrupted and has to be imported from another copy or recreated.
Since 2003 is the production version, I don't do any developing in 2007/2010 unless its for use only on those versions. My laptop runs 2010 and my desktop 2003.
RDP gets me what I need.
<then to open the file, change the conditional compilation variable and compile in 2010 for those machines>
Sounds like it could do so for you too, but OTOH you are well-versed in multi-version installation.
<automatically installed the 32 bit version>
Unless you nav'ed to the x64 folder and ran setup or downloaded the 64 bit Office then 32 bit is what installs.
The 64 bit version is still a little rough
http://www.pcworld.com/article/197415/beware_of_office_2010s_64bit_shortcomings.html
I know there's a whack of code changes that have to be made in moving to 64 bit VBA
http://msdn.microsoft.com/en-us/library/ee691831.aspx
That's my two bits :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks everyone. I finally got the virtual pc installed. Then got a2007 installed on it and A2010 64 bit installed on it. Am still having some API issues on 2010 but will post those separately.
But really, nice A2007 and A2010 are the *same* file format, do you really need both ?
mx