Error on connection string to Btrieve "database"

Hi Jen, it looks like a DSN doesn't exist for that database, which would make it easier.

If OLEDB is available, which it probably is if you're using .NET, you could use a connect string similar to this:

Provider=PervasiveOLEDB;Server=<server>;Data Source=<PathToDDFs> | <DSN Name>;User ID=<userid>;Password=<password>

If you want to use a DSN-less connection, just put the PathToDDFs in the Data Source parameter, or you can create a DSN through the Data Source Manager or ODBC Administrator and insert that DSN Name in the Data Source parameter.

Wayne Freeman
Analytica Business Systems
www.analyticabiz.com

A couple of quesitons:
- What version of PSQL/Btrieve are you using?  
- Are you using the OdbcConnection, OleDbConnection, or PsqlConnection object?  

Once you give the version of PSQL you're using, we can help with the Connection string.

The following C# code works for me with PSQL v8 and v9 (using the DSN DEMODATA).
using System;
using System.Data;
using System.IO;

namespace SimpleAdoNetConsole
{
      class Class1
      {
            [STAThread]
            static void Main(string[] args)
            {
                  try
                  {
                        OdbcConnection conn=new OdbcConnection("Driver={Pervasive ODBC Engine Interface};DBQ=DEMODATA;");
                        conn.Open();
                        // Create a SQL command
                        string SQLstr = "";
                        SQLstr = "SELECT * FROM CLASS";

                        OdbcCommand DBCmd = new OdbcCommand(SQLstr, conn);
                        OdbcDataReader myDataReader;
                        myDataReader = DBCmd.ExecuteReader();
                        Console.WriteLine("FieldCount: " + myDataReader.FieldCount.ToString());
                        \while (myDataReader.Read())
                        {
                              for (int i=0;i<myDataReader.FieldCount;i++)
                              {
                                    Console.WriteLine("Field " + i.ToString() + ": " + myDataReader[i].ToString());
                              }
                        }
                        myDataReader.Close();
                        conn.Close();
                        Console.WriteLine("Press Enter to continue");
                        Console.ReadLine();
                  }
                  catch (Exception ex)
                  {
                        Console.WriteLine(ex.Message);
                        Console.ReadLine();
                  }
                  
            }
      }
}

I am using version 8 and I am using OdbcConnection.
I am trying to use a DSN-less connection string because I do not have access to the server the database files are on, not to mention I don't want to create a DSN for every database I want to access because there are a lot of them.

Thanks~

Could it possibly have to do with security issues? If so, how would I figure out where the security issue lies?

Okay, with PSQL 8, you can't use the "Pervasive ODBC-32" driver because it doesn't exist.  You need to use the "Pervasive ODBC Client Interface" or the "Pervasive ODBC ENgine Interface".  

PSQL v8 doesn't really support using paths. You'd need to create at least a Pervasive Engine DSN on the server. Once you do that, you can use:
"Driver={Pervsive ODBC CLient Interface};ServerName=<servername>;ServerDSN=<serverDSN>"

So I would have to create a DSN for every database I want to access?

One the server, yes.  How many databases are you trying to access?

Yes, you would.  There are ways to automate that, though.

This will give you some hints about that:

http://www.analyticabiz.com/Updatearticlesview.php?ID1=51

Wayne
www.analyticabiz.com

Well, I'm not exactly sure yet. It could be anywhere between 10 and much more than that. :-/

If the DSN exists on each server, all you would need is the name of each one.  Are they the same name on every server?

Wayne

I'm not sure I understand what you're asking Wayne. The database files exist on one server. I'm understanding that I have to create a DSN for each database on that server.

Oh, okay, I thought you were accessing a number of servers.  I understand now.

Yes, you have to create a DSN for every database.  My suggestion on ways to automate that still stands, but you would have to weigh the effort of each method of automation against the probably less effort of just doing it through the wizard.

My experience has been that creating one DSN through the wizard and then exporting, modifying, and re-importing the registry entries is fairly easy.

Wayne

THere are other ways to automate creating the DSN/DBNs as well using DTO/DTI functions from the Pervasive SDK.  

Are you saying you've got 10+ sets of DDFs and data files and need to access each one?  

That is correct.
There is a way I just found out to be able to dynamically create DSN's, but I haven't started messing with it yet to find out if it will work or not. What do the DTO/DTI functions from the Pervasive SDK do?

Thanks for the info and help guys!
~Jen