64-bit ODBC driver for MS Access

[Guest]

I have several websites that use MS Access as the backend. I've now replaced
my development machine and installed Vista 64-bit, with Office 2007.

I am able to continue to develop the sites (Dreamweaver), but I'm unable to
test them locally due to the lack of an 64-bit ODBC driver.

I've read various discussions regarding recompiling for x86 32-bit
environment, but that doesn't work for me as this is IIS based, not a VB.NET
or C++ application.

Can anyone help me with a pointer or two in how to get around this problem.

The ideal situation of course is for Microsoft to produce a 64-bit ODBC
driver, and I'm sure this is in the pipeline, but the pipeline doesn't help
me now.

 

[Todos Menos [MSFT]]

uh.. what are you using ODBC for?

Jet?

ROFL

use SQL Server kid


-Todos

 

[Tony Toews [MVP]]

This person is not a Microsoft employee. This posting is almost
certainly by A a r o n K e m p f.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Todos Menos [MSFT]]

and for the record, http://babelfish.altavista.com tells me that
'Anything But Microsoft' gets translated to 'Todos Menos Microsoft'

ROFL

 

[Todos Menos [MSFT]]

Warning!

Tony Toes is _NOT_ a good source of advice for databases

he is a JET _FAIRY_

 

[Guest]

Excuse me guys, how come my question has turned into a battleground ???

I'm using Access BECAUSE SQL Express is not a supported option offered by
the ISP's.

Having a MS Access DB and connecting to it using ODBC is STILL the simplest
way of adding DB functionality to a website.

My question is still valid. How do I test an MS Access driven website on
64-bit Vista which does not seem to have a 64-bit ODBC driver for MS Access.

 

[susiedba]

dude are you on crack?

i've read it in 100 different places that MDB is strongly reccomended
against for web server deployments


a) it doesn't suppot multiple users
b) it doesn't support multiple users
c) you don't want to shut down the whole web server to compact /
repair


your question turned into a battleground because anyone using MDB for
anything should be fired and then spit upon


a) Vista you can't run as a web server
b) 64bit odbc will -NEVER- get here
c) find a new ISP and spend the extra $2/month in order to use SQL
Server

don't be a cheapskate when it comes to your database


if you care enough to build a database; use SQL Server

 

[Tony Toews [MVP]]

i've read it in 100 different places that MDB is strongly reccomended
against for web server deployments


a) it doesn't suppot multiple users
b) it doesn't support multiple users

You are correct in that MDBs are not recommended for web servers with any volume of
updates. Which is 98% of web servers. However Michael Kaplan has happily run his
website with all the multi-lingual pages being served an Access MDB

However Access is happily multi-user in a LAN.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Susie DBA [MSFT]]

in a LAN
but not on a WAN or a VPN or wireless or the public internet

all of which work PERFECTLY using Access Data Projects


I just don't have time to sit around and make ROI statements for every
little database I build.
It's easier to build EVERYTHING using SQL Server-- because SQL Server
is a better, easier development environment.

anyone using MDB for anything should be fired and then spit upon.
and yes; I'm including Michael Kaplan

anyone using MDB for anything should be fired and then spit upon

ADP is a superior interface / platform / architecture

I mean-- it's the same price
and it's compatible

and it's EASIER TO MANAGE

what are you gonig to do; bounce the webserver so you can compact and
repair?

ROFL

 

[Susie DBA [MSFT]]

Access doesn't scale to half dozen users and 20 mb of data.

I've seen it 100 times.

locking problems, indexing corruption, data corruption (why is one
record unicode?)

ROFL

seriously guys

SQL Server is the same price; or if it's $2/month or $20/month IT IS
WORTH IT