Prev: Calculating comboboxes
Next: How to find the name of the present subform
From: mat on 29 Mar 2010 20:14
Using Access 2003 I've been able to use passthrough queries to sql
server 2005 for a long time. In setting up a windows 7 64 bit
workstation I'm having issues that I can't resolve so far.

Normally a connections string like this would work:

ODBC;Driver={SQL Native Client};Server=blink
\sqlexpress;Database=mydb;UID=test_login;PWD=secret

That connection uses sql auth. All I've changed is the server name (old
instance and new instance both run against local copies of sql express).

I suspect that it's the 64 bit vs 32 bit driver thing, which I don't
really have a handle on. When I'm using a dsn I have to start the 32 bit
version of the odbc connection manager to get dsns that Access 2003 can
'see' when linking. Is something like this in play here? I've searched
but not found any solution for this yet.
From: Dennis on 30 Mar 2010 14:49
This is probably completely WRONG, but it's something I discovered only a
week or two ago. I attempted to set up a new ODBC connection with the "SQL
Server" type. That failed completely. After some research, I determined that
I had to install the "SQL Server Native Client 10.0" type. Once I did that,
the new ODBC connection worked perfectly. Again, this probably has NOTHING to
do with your issue, but.... You know...?



"mat" wrote:

> Using Access 2003 I've been able to use passthrough queries to sql
> server 2005 for a long time. In setting up a windows 7 64 bit
> workstation I'm having issues that I can't resolve so far.
>
> Normally a connections string like this would work:
>
> ODBC;Driver={SQL Native Client};Server=blink
> \sqlexpress;Database=mydb;UID=test_login;PWD=secret
>
> That connection uses sql auth. All I've changed is the server name (old
> instance and new instance both run against local copies of sql express).
>
> I suspect that it's the 64 bit vs 32 bit driver thing, which I don't
> really have a handle on. When I'm using a dsn I have to start the 32 bit
> version of the odbc connection manager to get dsns that Access 2003 can
> 'see' when linking. Is something like this in play here? I've searched
> but not found any solution for this yet.
> .
>
From: mat on 30 Mar 2010 18:45
Thanks for the reply...I do think it's in another direction though. The
driver you installed ought to server sql 2008, and I'm working with
2005. I don't have other odbc connectivity issues with this workstation
or server, using dsn, other than needing to use the 32 bit odbc
management tool.

It would seem to be a fair guess that {SQL Native Client} points to the
64 bit version of the odbc driver on a 64 bit windows os, but even if
it's a good guess I don't know how to beat it, and have found nothing re
this on the net so far.

In article <80DDDF9C-2ED4-4C55-AE2B-96594ED69AB7(a)microsoft.com>,
Dennis(a)discussions.microsoft.com says...
>
> This is probably completely WRONG, but it's something I discovered only a
> week or two ago. I attempted to set up a new ODBC connection with the "SQL
> Server" type. That failed completely. After some research, I determined that
> I had to install the "SQL Server Native Client 10.0" type. Once I did that,
> the new ODBC connection worked perfectly. Again, this probably has NOTHING to
> do with your issue, but.... You know...?
>
>
>
> "mat" wrote:
>
> > Using Access 2003 I've been able to use passthrough queries to sql
> > server 2005 for a long time. In setting up a windows 7 64 bit
> > workstation I'm having issues that I can't resolve so far.
> >
> > Normally a connections string like this would work:
> >
> > ODBC;Driver={SQL Native Client};Server=blink
> > \sqlexpress;Database=mydb;UID=test_login;PWD=secret
> >
> > That connection uses sql auth. All I've changed is the server name (old
> > instance and new instance both run against local copies of sql express).
> >
> > I suspect that it's the 64 bit vs 32 bit driver thing, which I don't
> > really have a handle on. When I'm using a dsn I have to start the 32 bit
> > version of the odbc connection manager to get dsns that Access 2003 can
> > 'see' when linking. Is something like this in play here? I've searched
> > but not found any solution for this yet.
> > .
> >


From: Stefan Hoffmann on 31 Mar 2010 03:32
hi Mat,

On 30.03.2010 02:14, mat wrote:
> Using Access 2003 I've been able to use passthrough queries to sql
> server 2005 for a long time. In setting up a windows 7 64 bit
> workstation I'm having issues that I can't resolve so far.
Try a reinstall/repair of the client tools.

> Normally a connections string like this would work:
>
> ODBC;Driver={SQL Native Client};Server=blink
> \sqlexpress;Database=mydb;UID=test_login;PWD=secret
http://connectionstrings.com/sql-server-2005#p3

There is imho the version (10.0) missing in your string.


mfG
--> stefan <--

From: mat on 31 Mar 2010 11:01
In article <O6HldRK0KHA.4832(a)TK2MSFTNGP04.phx.gbl>, ste5an(a)ste5an.de
says...
>
> hi Mat,
>
> On 30.03.2010 02:14, mat wrote:
> > Using Access 2003 I've been able to use passthrough queries to sql
> > server 2005 for a long time. In setting up a windows 7 64 bit
> > workstation I'm having issues that I can't resolve so far.
> Try a reinstall/repair of the client tools.
>
> > Normally a connections string like this would work:
> >
> > ODBC;Driver={SQL Native Client};Server=blink
> > \sqlexpress;Database=mydb;UID=test_login;PWD=secret
> http://connectionstrings.com/sql-server-2005#p3
>
> There is imho the version (10.0) missing in your string.
>
>
> mfG
> --> stefan <--

But I'm not working with 10.0, it's 9.0, and for that version the
integer has never been required. Not sure if it would even work.

What client tools are you referring to? The Access db has been repaired
etc.
 |  Next  |  Last
Pages: 1 2 3
Prev: Calculating comboboxes
Next: How to find the name of the present subform