Re: SQL 2005 linked server to Access 97
- From: "Mary Chipman [MSFT]" <mchip@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 11 Dec 2007 13:29:41 -0500
Access 97 is a tough nut because it's not supported any more. When you
run sp_addlinkedsrvlogin, try Admin with a blank '' password and see
if that helps.
By any chance is the A97 mdb you're trying to link to secured using
user-level security? That is a stumbling block with linked servers.
You can get around it by tinkering with registry entries, but if I
remember correctly, it only works for one mdb. IOW, if you have
another Access mdb you can't create a linked server to link to it.
-Mary
On Thu, 6 Dec 2007 17:47:00 -0800, wvmitchell
<wvmitchell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Need to create a linked server from SQL 2005 to Access 97. I am using the.
following:
EXEC master.dbo.sp_addlinkedserver
@server = N'TEST97',
@provider = N'Microsoft.Jet.OLEDB.4.0',
@srvproduct = N'Microsoft Access',
@datasrc = N'C:\BILL\Test97.mdb'
EXEC master.dbo.sp_addlinkedsrvlogin
@rmtsrvname=N'TEST97',
@useself=N'False',
@locallogin=NULL,
@rmtuser=NULL,
@rmtpassword=NULL
GO
Using Win 2003 R2 Standard with SQL 2005 Standard, it all works. But on dev
PC:
Win XP Pro SP2 with SQL 2005 Developer, it appears to create the linked
server, but cannot access any of the data in the Access file.
It works with an Access 2000 file on both systems. The Access 97 is a
3rd-party app, so can't upgrade the version.
Is this a limitation of Developer, or is there a config problem on dev PC?
Thanks, Bill Mitchell
- Follow-Ups:
- Re: SQL 2005 linked server to Access 97
- From: wvmitchell
- Re: SQL 2005 linked server to Access 97
- Prev by Date: RE: Multiple DB sessions and tcp ports limitation
- Next by Date: Re: SQL 2005 linked server to Access 97
- Previous by thread: Multiple DB sessions and tcp ports limitation
- Next by thread: Re: SQL 2005 linked server to Access 97
- Index(es):
Relevant Pages
|
