Last post Jan 21, 2009 07:02 AM by T. R. Tinker
Feb 20, 2006 04:25 PM|b8ball02|LINK
We just set up new server with OS Windows Server 2003 x64 to run SQL Server 2005 x64. We've also decided to run all of our ASP.net programs off this server. Now heres the problem, I'm being told microsoft doesn't have or plan to have support for 4.0 Jet
Database engine on x64 OS, so can anybody give me some ideas on how to connect to a Access Database on a x64 system.
Thanks in advance,
Jan 21, 2009 07:02 AM|T. R. Tinker|LINK
You can try the steps to switch between the 32-bit and 64-bit versions of ASP.Net in this srticle:
http://support.microsoft.com/default.aspx?scid=kb;en-us;894435 but it didn't work for me... When I set ASP.Net to the 32-bit version, as descibed, I got back 404-Not Found errors
on all of my web sites, but perhaps it will work for you.
If you Google the topic, you'll find lots of hits and suggestion for how to do this, most are incomplete or simply don't work (and several forced me to resort to a repair installation of Windows XP X64). The MSDN article referenced above is at least complete
and accurate, and also provides the steps to revert to the 64-bit version if necessary.
I'm stuck with a web application that has to use an Access database and no options for converting it to any flavor of SQL Server, so I am also very interested in learning of a way to use Jet 4.0 on an X64 OS.
It is not at all true that Microsoft doesn't now and doesn't plan in the future to provide Jet 4.0 support on an X64 platform: it is supported and included in X64 Enterprise Edition and will continue to be supported on that platform in the future to provide legacy
support for current EE installations.
It's pretty sad that operating systems as terrific as I'm finding XP X64 and Vista X64 to be have this deficiency. Afterall, Microsoft retains the ancient and useless FAT and DLL strategies for legacy compatibility through the most current and the latest Beta platforms.
Please let us know if you find the solution? I don't want to be forced back to a 32-bit operating system if there's a solution.