Ms Access 2003 Development on a Win 7 Ult machine
I purchased some new Win 7 Ult computers close to 2 years ago. We immediatley had an issue distributing Access 2003 applications developed on the Win 7 machine to clients still running Win XP on their computers.
I posted on EE and found out the issue is with ADO. We use ADO extensively so converting all of the file handling to DAO was not feasible and I didn't want to change everything to late binding. I also downloaded some suggested DLL's and that didn't resolve the issue either.
To get around the issue we have been doing all of our Access 2003 development on the old XP machines. It is much slower to develop but it eliminates the problem of developing on the Win 7 and distributing to the XP machines.
At the suggestion of some others I recently installed XP Mode on the Win 7 machine. I installed a seperate copy of Access 2003 on the XP virtual machine. Access was already on the Win 7 machine. I did some testing by working on some applications with heavy ADO usage, using Access 2003 in the XP Mode vitual machine. When I transferred the apps to a stand alone XP machine they seem to work fine. No ADO issues.
My question: My testing has been limited but I am now wondering. If I do all my Access 2003 development in XP mode on the Win 7 machine will I eliminate the ADO issues that I had when developing Access 2003 apps in native Win 7? My initial testing tells me it will eliminate the issue but I don't want to start sending apps out to clients and encountering issues.
I thought maybe some EE'ers would know for sure.
I posted on EE and found out the issue is with ADO. We use ADO extensively so converting all of the file handling to DAO was not feasible and I didn't want to change everything to late binding. I also downloaded some suggested DLL's and that didn't resolve the issue either.
To get around the issue we have been doing all of our Access 2003 development on the old XP machines. It is much slower to develop but it eliminates the problem of developing on the Win 7 and distributing to the XP machines.
At the suggestion of some others I recently installed XP Mode on the Win 7 machine. I installed a seperate copy of Access 2003 on the XP virtual machine. Access was already on the Win 7 machine. I did some testing by working on some applications with heavy ADO usage, using Access 2003 in the XP Mode vitual machine. When I transferred the apps to a stand alone XP machine they seem to work fine. No ADO issues.
My question: My testing has been limited but I am now wondering. If I do all my Access 2003 development in XP mode on the Win 7 machine will I eliminate the ADO issues that I had when developing Access 2003 apps in native Win 7? My initial testing tells me it will eliminate the issue but I don't want to start sending apps out to clients and encountering issues.
I thought maybe some EE'ers would know for sure.
ASKER
Thank you for your response. Have you actually used this solution and it worked or are you guessing that it will work?
I am hoping to hear form someone that has actually used this solution to resolve the issue.
I am hoping to hear form someone that has actually used this solution to resolve the issue.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm not familiar with the problem you have, but I've developed .NET apps with ADO with no issues. I also manage some A2007 apps in a Win7 enviro and have no issues with the ADODB recordsets being used. We just upgraded to O2010 last week and haven't had any issues there either.
My computer does have all its shots, but ADO issues would just seem like a reference is missing or corrupted.
My computer does have all its shots, but ADO issues would just seem like a reference is missing or corrupted.
Check the references on both version of windows. Try to use the same library version.
Developing on a virtual machine should add no problem to the project. Virtual machine is meant to run software that misbehave under higher versions of operating system.