Access 2010 & Runtime problems with Windows XP
We use Microsoft Access to produce various front end programs for use with SQL Server databases. We then distribute these frontend programs using the Access Packaging Wizard and Access Runtime system.
We run two servers, one local server running SBS 2011 and SQL Server 2008R2 and one dedicated remote server (cloud server) running Windows Server 2003 and SQL Server 2005.
Most of our client computers operate on Windows 7 Professional (both 32 bit and 64 bit processors) but we have some remote workers working on Windows 7 home edition, one working on Windows Vista and one working on Windows XP.
We have recently upgraded to Access 2010 for programming the frontend system to be compatible with SQL Server 2008R2. Previously we were using Access 2007.
We are having compatibility problems with the Windows 7 home, Windows Vista and Windows XP remote computers when we try to run Access 2010 runtime system and a frontend program created and packaged in Access 2010 that tries to connect to the Cloud server running SQL Server 2005.
Debugging faults that only show up when running via a runtime version of Access is quite problematic but I have tried to pin down the problems as best I can.
It seems that the problems are likely to do with different version of Microsoft ActiveX Data Objects in that I have pinned down one of the problems in the Access Basic code to the first “set variable = currentproject.connection”
If we install a full version of Access 2010 on a spare Windows XP machine and open the .adp version of the frontend then the program works correctly. If we open the .accdr version from the packaged frontend using Access 2010 runtime the frontend fails with an illegal command. If we open the .accdr version with Access 2010 runtime version on a Windows 7 Professional machine then the frontend works correctly.
The problems seem to be variable depending on the operating system in use, from illegal commands to the frontend seeming to work correctly except some queries do not return any data.
Assuming that my idea is correct, is there a version of Microsoft ActiveX Data Objects that is compatible with both Access 2007 and 2010 (including the runtime systems) and Windows XP, Windows Vista, Windows 7 Professional and Windows 7 Home?
We currently have the offending systems functioning correctly by packaging the .adp version of the front end using Access 2007 and running Access 2010 runtime on the computer. Both Access 2007 runtime and Access 2010 runtime are installed. I believe we now have quite a muddle of Access installation packages which probably means there is some cross contamination of versions of support systems. I mention this as the Access 2007 packaged frontend does not work with Access 2007 runtime although it use to before Access 2010 was introduced to the picture.
We run two servers, one local server running SBS 2011 and SQL Server 2008R2 and one dedicated remote server (cloud server) running Windows Server 2003 and SQL Server 2005.
Most of our client computers operate on Windows 7 Professional (both 32 bit and 64 bit processors) but we have some remote workers working on Windows 7 home edition, one working on Windows Vista and one working on Windows XP.
We have recently upgraded to Access 2010 for programming the frontend system to be compatible with SQL Server 2008R2. Previously we were using Access 2007.
We are having compatibility problems with the Windows 7 home, Windows Vista and Windows XP remote computers when we try to run Access 2010 runtime system and a frontend program created and packaged in Access 2010 that tries to connect to the Cloud server running SQL Server 2005.
Debugging faults that only show up when running via a runtime version of Access is quite problematic but I have tried to pin down the problems as best I can.
It seems that the problems are likely to do with different version of Microsoft ActiveX Data Objects in that I have pinned down one of the problems in the Access Basic code to the first “set variable = currentproject.connection”
If we install a full version of Access 2010 on a spare Windows XP machine and open the .adp version of the frontend then the program works correctly. If we open the .accdr version from the packaged frontend using Access 2010 runtime the frontend fails with an illegal command. If we open the .accdr version with Access 2010 runtime version on a Windows 7 Professional machine then the frontend works correctly.
The problems seem to be variable depending on the operating system in use, from illegal commands to the frontend seeming to work correctly except some queries do not return any data.
Assuming that my idea is correct, is there a version of Microsoft ActiveX Data Objects that is compatible with both Access 2007 and 2010 (including the runtime systems) and Windows XP, Windows Vista, Windows 7 Professional and Windows 7 Home?
We currently have the offending systems functioning correctly by packaging the .adp version of the front end using Access 2007 and running Access 2010 runtime on the computer. Both Access 2007 runtime and Access 2010 runtime are installed. I believe we now have quite a muddle of Access installation packages which probably means there is some cross contamination of versions of support systems. I mention this as the Access 2007 packaged frontend does not work with Access 2007 runtime although it use to before Access 2010 was introduced to the picture.
First: Access 2010 is not compatible with some of your operting systems, it would seem. This is from the Requirements for 2010 (http://technet.microsoft.com/en-us/library/ee624351.aspx#section6), under the "Operating System" requirements section:
"Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1, Windows Server 2003 SP2 and MSXML 6.0 (32 bit Office only), Windows Server 2008 or later (32-bit or 64-bit), Windows 7 operating system."
I would strongly suspect that your troubles are not in ADO, but instead will lie in incorrect or missing references on some of those machines. While you might be failing on the CurrentProject.Connection,
Can you listout the references that you're using in the database?
I would also strongly encourage you to finalize your deployment environment, and take steps to insure that your clients adhere to those specs. If you're going to work with Access 2010, then upgrade all of your clients to the 2010 Runtime - and make SURE that those clients are (a) running a compatible operating system and (b) fully updated on Windows and Office.
"Windows XP with Service Pack (SP) 3 (32-bit), Windows Vista with SP1, Windows Server 2003 SP2 and MSXML 6.0 (32 bit Office only), Windows Server 2008 or later (32-bit or 64-bit), Windows 7 operating system."
I would strongly suspect that your troubles are not in ADO, but instead will lie in incorrect or missing references on some of those machines. While you might be failing on the CurrentProject.Connection,
Can you listout the references that you're using in the database?
I would also strongly encourage you to finalize your deployment environment, and take steps to insure that your clients adhere to those specs. If you're going to work with Access 2010, then upgrade all of your clients to the 2010 Runtime - and make SURE that those clients are (a) running a compatible operating system and (b) fully updated on Windows and Office.
ASKER
I will try to answer your points as best as I can.
Barbobrave - Unfortunately 2010 applications do not function using 2010 runtime on the older operating systems.
LMSConsulting
Your point is well made about switching all users to a more up to date system and maybe this will be the easiest solution.
To answer your other points. I do not know how to check broken references when there is only a runtime system on a machine so I cannot be sure if there are any. All machines have Office 2010 (without Access) on them. The references that are used are:
Visual Basic Applications
Microsoft Access 14.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft Calander Control 2007
Microsoft Excel 14.0 Object Library
Microsoft Outlook 14.0 Object Library
Microsoft ActiveX Data Object 2.8 Library
I believe all the machines comply with the Service Packs you mention but I have not been able to check them all at present.
My guess is the probelm relates to Microsoft ActiveX Data Object 2.8 Library. I do not know if there a valid version suitable for all the operating systems I'm having problems with. I find it easy to accept that Windows XP will not be compatible but I would have thought Vista and Windows 7 Home should not be giving problems.
Thanks for your input.
Barbobrave - Unfortunately 2010 applications do not function using 2010 runtime on the older operating systems.
LMSConsulting
Your point is well made about switching all users to a more up to date system and maybe this will be the easiest solution.
To answer your other points. I do not know how to check broken references when there is only a runtime system on a machine so I cannot be sure if there are any. All machines have Office 2010 (without Access) on them. The references that are used are:
Visual Basic Applications
Microsoft Access 14.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft Calander Control 2007
Microsoft Excel 14.0 Object Library
Microsoft Outlook 14.0 Object Library
Microsoft ActiveX Data Object 2.8 Library
I believe all the machines comply with the Service Packs you mention but I have not been able to check them all at present.
My guess is the probelm relates to Microsoft ActiveX Data Object 2.8 Library. I do not know if there a valid version suitable for all the operating systems I'm having problems with. I find it easy to accept that Windows XP will not be compatible but I would have thought Vista and Windows 7 Home should not be giving problems.
Thanks for your input.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think you are right about the version of ADO. I suspect I will need to try each earlier vesion until everything works or there is a compatability issue. I'm not aware of using any advanced feature so it should be ok.
It might be easier to upgrade the older kit and move on.
Thanks for your help.
It might be easier to upgrade the older kit and move on.
Thanks for your help.
It seems to be a merely runtime version problem?