- #MICROSOFT ACCESS DATABASE ENGINE 2007 X64 INSTALL#
- #MICROSOFT ACCESS DATABASE ENGINE 2007 X64 DRIVERS#
- #MICROSOFT ACCESS DATABASE ENGINE 2007 X64 DRIVER#
- #MICROSOFT ACCESS DATABASE ENGINE 2007 X64 UPGRADE#
I'm attempting to install the Microsoft Access Database Engine 2010 Redistributable (64-bit) on my system to overcome this limitation.
#MICROSOFT ACCESS DATABASE ENGINE 2007 X64 DRIVERS#
Under this configuration, SQL Server cannot utilize the JET database engine drivers via a linked server or the OpenRowset/OpenDataSource functions, since JET is 32-bit, and SQL/OS is 64-bit. However I doubt this is your situation unless you're running XP or something.I have a laptop with VISTA Ultimate 64-bit OS, with Sql Server 2008 64-bit and MS Office 2007 (32-bit) installed. If you are running an x86 bootstrapper then you'd need to load the 圆4 registry view which is doable, just requires more code. Var installed = !String.IsNullOrEmpty(value) //Or compare to value of `Installed`
#MICROSOFT ACCESS DATABASE ENGINE 2007 X64 DRIVER#
Perhaps something like this: var value = Drivers\Microsoft Access Driver (*.mdb)", "") as string Therefore build the bootstrapper as an 圆4 app (uncheck the prefer 32-bit flag if it is set in your project). Since you are probably running at least Win7 on all machine now you are likely running on an 圆4 platform only already.
How you do this depends on how you build your bootstrapper. To determine if 圆4 Access is installed you'll need to look at the 圆4 registry.
If you need to be able to make builds of both versions for a while then of course this would be more difficult. Then just install the new version on new computers. If you're updating only when you replace machines then do you need to be able to make updates to the x86 version anymore? If not then you can skip all this and just go ahead and recompile your existing code as 圆4 only.
#MICROSOFT ACCESS DATABASE ENGINE 2007 X64 UPGRADE#
When the upgrade is finally complete you can revert back to just the single app for 圆4 without the bootstrapper and no one will know. Redeploy your app and users will be running one or the other depending on situation. If it is then it starts the 圆4 version of your real app otherwise it starts the x86 version instead. This bootstrapper program looks to see if the 圆4 Access driver is available. Then create an Any CPU app that has the same name as your main program (e.g. They should produce different binaries in different directories (e.g. At this point I would set up your build process to build both an x86 and 圆4 version of your app explicitly. If that isn't an option for some reason then you have little flexibility. Then you are using the Access 圆4 driver (assuming you set up DSN correctly) and can remove the x86 Access driver at your leisure. Then change the compiler flag to not prefer x86, recompile and redeploy your app. My personal thought is that you should leave your app unchanged and targeting x86 (with Access x86 driver) until all the machines have been updated to 圆4. There is a way to install the Access 圆4 Database Engine with Office x86 installed (and hence you will have both x86 and 圆4 Access drivers installed as documented in several places. Either you aren't using Office (which means you don't need Access) or you are also upgrading at the same time to 圆4 of Office (which means some addins won't work anymore). I'm curious if your admin team has worked around the issue that you cannot install Access 圆4 Database Engine with the standard Office x86 installed. If you were to disable this behavior then suddenly your app would be running 圆4 on Win64 (your future goal) but you haven't yet updated the drivers. There really isn't a good workaround because your app is going to run as x86 even on Win64, as you want it to. The default behavior in this case is to run as x86 even on 圆4 machines. I presume that your app is a VB.NET app and that you're compiling for Any CPU.
0 kommentar(er)
