+ Reply to Thread
Results 1 to 3 of 3

MS Query Issues - Insufficient Connection Info. Driver's SQLSetConnectAttr failed

  1. #1
    Registered User
    Join Date
    12-06-2007
    Posts
    2

    MS Query Issues - Insufficient Connection Info. Driver's SQLSetConnectAttr failed

    Hi Guys,

    I'm new to this forum but I was hoping someone could help me out with this frustrating MS Excel query issue we are experiencing. We are going through a PC replacement exercise at work at the moment. Some finance staff are getting new machines others are not. All staff with new PCs can no longer access any existing MS queries or open any new queries that they save. Existing/old PC users have no trouble with any of this.

    The error presents itself when we open Excel (on the new PCs) goto the 'Data' menu, select 'Import external data' (the Choose Datasource Window appears), goto 'Queries' tab, select an existing query from the list and click 'Open' then we get the following errors :

    Insufficient Connection Information was supplied
    Driver's SQLSetConnectAttr failed

    we then Click OK then......

    asecond error appears which is : Couldn't read this file (Click OK or Help)


    We have tried a number of things including opening the queries from the old PCs, copying the SQL statements and creating new queries, saving them and trying to open them up on the new PCs but same error. We also tried installing ASAP utilities which was posted on another forum but it didn't make any difference except for slowing down the complete Excel operation on that PC. I don't want to create more issues. After removing the ASAP utlity it was back as it was before.

    On PCs were it works it asks you for the OBDC connection first and my understanding is there are passwords stored in the queries themselves - maybe one of these have changed ? I don't really know.

    How/where can you access this configuration in MS Query. Is it possible ? Is it in the registry somewhere ??? Does it have to do with the DSN itself or Excel having some security enhancements. The Finance users are all running Microsoft Office Excel 2003 (11.8169.8172) SP3) part of the MS Office Professional Edition 2003.

    Any ideas anyone ????


    Thanks,

    Dave

  2. #2
    Forum Moderator Leith Ross's Avatar
    Join Date
    01-15-2005
    Location
    San Francisco, Ca
    MS-Off Ver
    2000, 2003, & 2010
    Posts
    23,258
    Hello Dave,

    It is difficult to say where the problem is with the limited information you have posted. You don't say anything about your system or software. What financial program are you using Sage, Pegasus, Exchequer, what? Is the connection to a local server or remote? What software is running on the PCs that do work? Have you checked your software manual for proper SQL configuration?

    Sincerely,
    Leith Ross

  3. #3
    Registered User
    Join Date
    12-06-2007
    Posts
    2
    Thanks for the reply. I understand it is difficult to interpret without a full rundown.

    We are running the Civica Local Government application called Authority on our Corporate Informix database. The GDC (Genero Desktop Client) runs on each PC & manages all the 4js program that run from the Authority menu. The Authority program includes all Financial modules ie. General Ledger, Accounts Payable, Bank Reconciliation, Purchasing plus many others. The corporate server is a local server. We do also provide a remote connection thru Citrixbut the problematic PCs all connect to the 'local' Corporate server. Everything works on each of these problematic PCs except for the Excel/Query operation ie. opening and creating-saving SQL queries. We have tried saving the queries to the Microsoft default directories and also to other drive mappings that we have added. We can browse to all these locations through Excel but it just doesn't allow us to save to that location. The queries are visible in these directories but you can't open them.

    The saved scripts all access our corporate Informix database. The issue is not specific to Informix however as if we try to create an query to an Access database, we can run the query fine at the time it is created but when it comes to saving the query we get the same error as per original post. It doesn't make sense. I just can't find any info anywhere on the web and I'm abit surprised as this issue surely has cropped up somewhere else unless if there is a new trend these days where no one updates there PCs ???? Not sure if anyone knows much about re-installing an ODBC add-in ? Could that be the issue ?? Thanks

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Search Engine Friendly URLs by vBSEO 3.6.0 RC 1