[AccessD] Linked to SQL Server in a domain

Hi Jim

I believe Oracle was and still is a different matter. As I remember, you had to install an "Oracle client", a monster app with all sorts of tweaks and settings.
On the other hand, the only trouble I've seen with the SQL Server ODBC client was that in the old days it defaulted to Named Pipes. Change this to TCP/IP and you were off.
Of course, if you design an app from scratch you would hardly aim for ODBC these days.

/gustav


>>> accessd at shaw.ca 22-05-2009 19:28 >>>
Hi Gustav:

My first major conversion project was over 10 years ago when a client was
trying to get some decent performance out of an Access/Oracle application.
They were initially using the query/link/pass-through technology and they
had all but given up on the project... I tried out the ADO-OLE method and
had stellar results.

I did briefly work with ODBC but found that unless the application was
supported locally it was too difficult to try and get a client to install
the driver... through the phone or via email. On the other hand ADO, with
its remote capabilities, is built in to all Windows systems. 

Hardware Performance has dramatically improved in the last 10 plus years so
some of the issues of the past are irrelevant now but I have never looked
back.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Friday, May 22, 2009 12:29 AM
To: accessd at databaseadvisors.com 
Subject: Re: [AccessD] Linked to SQL Server in a domain

Hi Jim

That is not my experience. We had several apps running at clients for years
using A97, ODBC and the SQL Server prior to 2000 (version 7? Can't remember)
without a single issue.

So at least in some cases ODBC works.

/gustav

>>> accessd at shaw.ca 22-05-2009 07:00 >>>
Hi John:

I have been working with MS Access to ADO-OLE to MS SQL/Oracle DBs since
1997 and Access does not work with ODBC. There is a simple and stupid way to
up date an old Access MDB to a MS SQL BE using connection/links. 

This system actually works fine for delete, add and update... but as soon as
you start grabbing recordsets of data for reports, subforms or start rolling
out a new application to a remote desktops the whole system grinds to a
halt. At that point you have reached the end of the usefulness of the ODBC
connections.

Unfortunately there is no short cut, the client and you just have to bite
the bullet and go straight ADO-OLE... It is not that difficult but the nice
gui interface within Access can not do it.

Jim