Access Database and x64 OleDB Connect

Go the msdn product feed back center and make a suggestion. I feel they should have 64 bit drivers available for odbc also.

http://lab.msdn.microsoft.com/productfeedback/

KenTucker at 2007-9-9 >

Hi - I'm really hoping you can help, enlighten or point me in the right direction

I'm not technical when it comes to Access, ASP and their combination to provide web applications (dbases etc). I hope this info gives you enough information to work from (web - Access - ASP) to know where our problem lies and apologise for my lack of knowledge.

My problem is that after installing server 2003 64bit enterprise on 64bit hardware, my web designer says that they cannot get the Access (office 11 version) database to work. Access (the program) opens and the actual dbase opens within the program via remote access.

However, when we apply the new IP, swapping servers, the backend systems seem to fail to work so we cannot login for example to the web secure area

I cannot find any mention on the net to this effect where people have an incompatibility issue so I assume there is a way to allow Server 2003 Enterprise 64bit running on a 64bit architecture to run Office 2003 professional (and in particular Access).

Not knowing about ASP, is it that they do not use ASP.net v2.0?

Or does the server require setting up in a particular way to allow for everything to work together.

I hope you can help with the above in anyway as I'm pulling teeth trying to get to the bottom of why our Chinese web designers cannot get it to work - in turn making us look stupid in our clients eyes since they expected our new server online over a week ago

Thanks, Liam

juliam at 2007-9-9 >

Hi Ken

I'm assuming this was primarily meant as an answer for my query for me to follow?

If so, thank you, will get them to try it and let the board know the outcome.

One thing, their using ASP and not ASP.NET, will this create delays in rewriting codes?

Ken Tucker wrote:

As you have probably figured out there is no way to set what processor to target in an web application. Try this. Install asp.net 2.0 32 bit version C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i Enable 32 bit applications on 64 iis cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 When you create the asp.net application do not use the file system create the application on the local iis. In the iis manager create a new application pool for the 32bit applications. Now open the properties for the web site you created. Change the application pool to the one you just created. Click on the configuration button and change extension mappings directory from C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll for all the extensions. Once this is done you should be able to open an access from inside a web page.

juliam at 2007-9-9 >

Thanks Ken

Can anyone else please advise:

1 - original Website backend uses MS Access 2003, ASP (not .NET), IIS6.0 on win2k server

2 - new server 64bit, win serv 2k3 ent 64bit, MS Access 2003, ASP (not .NET), IIS6.0 - dbase as a webpage will not open, cannot login for access to it (it opens ok within Access so the problem is not with Access 2003 or the dbase as it stands - it's with the structure to produce the dbase through the web on a x64 machine and OS)

Has anyone heard of this problem before (not ODBC related etc) - there must be someone else still using ASP to produce a simple MS Access dbase but on a server 2003 x64 machine. Please anyone?

Liam

juliam at 2007-9-9 >

I just want to know if Microsoft change is mind and decided to port Microsoft Jet Database engine to 64bit.

I don't understand this choice. Why migrate to x64 then ? Or is there an other mean to manipulate an Access BD with a x64 application ?

Thank you

Eric

allstar1234 at 2007-9-9 >