INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Unable to access db after upgrading to PSQL 9.50

Unable to access db after upgrading to PSQL 9.50

(OP)
Hy all

I successfully access tha data of a btrieve format database via the following ODBC DSN-less
connection using Pervasive.SQL 2000 Workstation engine and VB6.
.....
Dim adoConn As New ADODB.Connection
Dim rst As New ADODB.Recordset
With adoConn
    .Provider = "MSDASQL"
    .ConnectionString = "driver={Pervasive ODBC Client Interface};ServerName=;ServerDSN=;dbq="N:\database\man10";
    .Open
End With

rst.Open "select * from " & Chr$(34) & "deviation surveys" & Chr$(34) & " order by .....

After ugrading from Pervasive.SQL 2000 Workstation engine to Pervasive.SQL 9.50 Workstation engine
I run my application and i realised that i was no longer able to access tha data of my database, having the following error:

[Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface][Data record manager]No such table or object

I can create and access the database through Pervasive control center and if i use the engine DSN created with PCC into the vb6 connection string it works perfectly (..dbq=DSNdbname;).

Can anyone suggest where and how i can fix the connection string to let it work perfectly under PSQL 9.50?.

Thanks in advance

Benedetto
 

RE: Unable to access db after upgrading to PSQL 9.50

According to the docs, the DBQ parameter is the Database Name and does not support paths.  While older versions of PSQL may have supported paths, newer versions don't.  All of the docs I've got shows that the DBQ parameter is a database name and not a path.  This includes PSQL v8 and 2000i.

The solution for you is to create the database name on the server and use that in the connection string.

You can use the DTO object to create database names within your program.   

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
http://www.mirtheil.com

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close