I am using Microsoft SQL Server 2005 x64. I am trying to create a linked
server for an access 32-bit .mdb. I have installed the drivers for the
access connection on the machine. The providers show up under the 32-bit
version of the odbc administration tool; however they do not show up as a
selection under the providers tab under linked servers in the sql server
management studio. How do i allow the 64 bit sql server management studio
providers to list the 32 bit access provider. Is this possible?

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote

mike,

Sorry, but 64-bit executables (your SQL Server) cannot talk to 32-bit
executables (your Access provider). This is a fundamental feature of the
32/64 bit divide. One workaround is to:

1. Install a SQL Server 2005 Express (it is 32-bit, of course) instance.
2. Create a linked server from X64 server to Express. This uses the
communication protocols to talk between the servers, so the 32/64 divide is
not an issue.
3. Create a linked server from Express to Access. These are both 32-bit and
Express can call the Access provider.

I searched and found a description of this:
http://gorm-braarvig.blogspot.com/20...ql-200564.html

Truth in advertising, I have not done it, but I have seen that some people
have used it successfully. (Even though it made them feel cranky to work
this way.)

RLF


"mike" <mike (AT) discussions (DOT) microsoft.com> wrote