Cannot create file dsn with Pervasive 8

Posted on 2006-06-02
Last Modified: 2013-12-25
We just upgraded from Pervasive 7.

Have many Excel files linked to Pervasive via MsQuery using a File DSN.

On the workstatation the ODBC interface looks different for setting up a File DSN connecting via Pervasive ODBC.

In the advanced parameters we tried doing nothing extra, and also specfying the server and database.

We have not been able to create a File dsn no matter what.

We have been able to create a user dsn which works fine.
Question by:hertzgordman
    LVL 28

    Expert Comment

    by:Bill Bach
    We have always avoided File DSNs, as they have been somewhat unstable, and they do not work very well (as you have observed).

    Your best bet is to create one System DSN as a Pervasive Client DSN on each workstation, pointing to the Pervasive Engine DSN on the server.  This works VERY well, the only drawback being that you must go to each workstation and create the DSN.  If the extra workload is the problem, there are ways two solutions:
    1) Automate the DSN creation.  You can do this via:
      a) Registry imports
      b) Writing a standard MS/ODBC application
      c) Writing a Pervasive DTI/DTO application
    2) Use a DSN-less connection.  Instead of specifying the File DSN, have the application provide the needed Connection String to go right to the server.

    IN essence, the File DSN is only a tool for your users so they will not need to learn the ODBC Administrator. The information entered in a File DSN is the same general information that would be entered when creating a User or System DSN in the ODBC/32 Administrator.  You can try extract the information from a properly-created System DSN's registry settings & see if that works for you.
    LVL 28

    Expert Comment

    by:Bill Bach
    One other question -- you HAVE updated the client software on each workstation, right?  You cannot use the PSQL7 client to connect to PSQLV8.

    Author Comment


    Its not a big issue to recreate the DSN on the workstations.  I do believe using a System DSN gives the most scope.

    The problem is we have a number of Excel Documents referencing the the Btrieve data via MS Query.

    Some of these spreadsheets were created using a File DSN as the source.

    Without the File DSN on the workstation, the Excel documents will not work.

    That is why we need to recreate the File DSN on the Workstation.

    When we try to do this we are told that the DSN is "non-verified".  When we try to edit is we get a login prompt for Name and UserName.  We enter the correct info but then get another error message.

    My question is: it is not possible to create a File DSN with Pervasive 8?  If it is, do we need to enter advanced info in the configuration such as datbase and server?  In doing that, what is the correct syntax?
    LVL 28

    Accepted Solution

    They do work, but it can be a bear to set them up.  Here's one that worked on my workstation, connecting to a server named BWING and talking with an Engine DSN on that server called DEMODATA:

    DRIVER=Pervasive ODBC Client Interface

    If you are using SPX only, then remove the "TCP:" from the transport hint.  If you need security enabled, you may need to add UID and PWD entries.  See the ODBC driver information in the Pervasive manual for more details on optional connection string entries.

    Author Comment

    Thanks - will give this a try.

    Author Comment


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    Introduction: Often, when running a query with joins, the results show up "duplicates", and often, those duplicates can be "eliminated" in the results using DISTINCT, for example. Using DISTINCT is simple: just add it after the SELECT keyword, an…
    Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
    Video by: Steve
    Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
    Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

    760 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    6 Experts available now in Live!

    Get 1:1 Help Now