Linked Server to MS Access

  • All,

    Well, this is kind of three folds...

    1. the problem

    2. the solution

    3. any alternative

    1. the problem

    I receive a number of errors when trying to test connection to a linked server.

    The linked server is created to an MS Access file located in the program files folder.

    When I log into SSMS using Windows Authen, I successfully tested the linked server connection.

    When I log into SSMS using SQL Server Authen, the connection test results in a lot of errors... one error after another.

    Cause - After about three days trying to figure this crap out, I realized that the MDB file was locked. This locking is due to an automatic download service that another software is running to update the mdb file. Once i stopped the service, i am able to successfully test the connection using SQL Server Authen.

    Question: Why does this locking affect only SQL Server Authen from connecting to the Linked server?

    2. The solution

    Since the users front end does not require constant access to the MDB File, i am able to set a stored procedure to run automatically such that I can pull data from the mdb file into the sql server database while not having to stop the service.

    3. Is there any other solution to this problem?

    Regards

    Surendra

  • as an aside, I have not gotten a linked server for access to work in SQL 64 bit / any version; against either a .mdb or .accdb

    i can get the ACE drivers to work with Excel no problem

    would you mind scripting your linked server and posting it? maybe i can get one to work here.

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • exec sp_addlinkedserver @server='FTDP',

    @srvproduct= 'Access',

    @provider= 'Microsoft.ACE.OLEDB.12.0',

    @datasrc= 'C:\ftdp.mdb'

    you need to download the oledb.12.0 provider from microsoft website. just google it.

    my problem is becoming even more interesting. I installed sql server enterprise edition, installed a new instance and it worked... both server authen and windows authen accessed the linked server after the ms access database was locked.

    Well there were a few difference which i haven't gotten around to check whether this could be the cause of the problem:

    1. VIA is disabled on the new instance and in general.

    2. The new instance was configured to run on a specified user account. This is the same account i am using... its an administrator account and everything.

    3. Now i have sql server enterprise edition.

    So of the three, I am not sure which one solved the problem. But will update the forum when I figure this crap out.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply