Post reply

Link Server OLE DB Problem

  • October 17, 2007 at 10:16 am

    #176267

    I created a link server from SQL Server 2000 to FoxPro database using vfpoledb driver. SQL server and FoxPro database are NOT being run on the same machine. I am getting this error:

    Error 7302: Could not create an instance of OLE DB provider 'SQLOLEDB'. OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB returned x8007007f].

    When I test the link server on the machine which has FoxPro database , It is working with no problem.

    Anyone can help me?

    Thanks

  • October 17, 2007 at 10:27 am

    #742804

    I'm guessing you already tried the answer you found for yourself a few months ago?

    http://www.sqlservercentral.com/Forums/Topic403104-146-1.aspx

    Also check this out and see if it helps you...

    http://forums.mysql.com/read.php?60,19295,20586#msg-20586

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • October 17, 2007 at 10:57 am

    #742814

    Thanks Luke,

    I have already tried those suggestions. The link server works fine on the same machine with FoxPro. I couldn't solve the problem that I am having with the link server calls other machine to connect to the FoxPro database.

    Server1 - SQL Server 2000 (I created the link server)

    Server2 - FoxPro database

    Problem: When a user machine sends a query to Server1/Link Server, it is getting Error:7302

  • October 17, 2007 at 12:05 pm

    #742847

    Sure sounds like a client type of error. We get the same thing when we try to connect to Oracle when the Oracle client hasn't been installed on the server (twice as much fun with clusters). Does FoxPro have an equivalent client software?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • October 17, 2007 at 12:14 pm

    #742849

    For FoxPro, there is no client/server application type. Basically, All data stored in the server as FoxPro database files (*.dbc).

  • October 17, 2007 at 12:24 pm

    #742853

    I understand there's no server.

    If you built FoxPro app and had a shared database that more than one user was going to hit, each of the clients had some DLL or other that would enable them to connect to the FoxPro db. Simply having the FoxPro db file isn't enough. You have to have the software that enables the connection. Same with Access.

    This makes sense since the machine with FoxPro installed is having no issues accessing it.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • October 17, 2007 at 12:38 pm

    #742854

    The client is SQL client.

    FoxPro database is located on the shared drive.

    My problem is accesing to the datasource from SQL using the link server.

  • October 17, 2007 at 2:18 pm

    #742884

    Any other ideas?

  • October 31, 2007 at 1:21 pm

    #747227

    Have you tried setting up a DSN for connecting to FoxPr on the machine you are running the DTS package from. I ported over a FoxPro db to SQL Server 2005 two years ago, and I remember having to set up a DSN using the FoxPro driver in order to connect. I then set up a Linked Server via ODBC, after I created the DSN on the SQL Server machine.

    If you're using a 64 bit machine you have to install the 32 bit FoxPro driver in the WOW directory.

    Good Luck

Viewing 9 posts - 1 through 8 (of 8 total)

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