Contact US

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.

Students Click Here

Results of the Consistency tests in my PSQL 2000i DB...

Results of the Consistency tests in my PSQL 2000i DB...

Results of the Consistency tests in my PSQL 2000i DB...


We had recently moved to Pervasive 2000i from Pervasive 7.0 and have been facing problems following that...
We are having the problem of the DDFs not matching the existing btreive files. I had run the *consistency test* on my database and most of the tables had index inconsistency or Record length mismatches.
Here are the Statistics:

Pervasive.SQL Compatibility Mode  =  7
Tables Checked  =  269
Tables Passed  =  117
Tables Failed  =  152
Illegal Object Names  =  7
Record Length Inconsistencies  =  25
Variable Length Column Inconsistencies  =  0
Data Type Inconsistencies  =  0
Column Overlaps  =  0
Full Path (instead of Relative) Table Locations  =  0
Table Files Don't Exist  =  1
Index Inconsistencies  =  519
System Table Inconsistencies  =  0
General Dictionary Inconsistencies  =  1

Here is my basic standpoint on the issues:

Illegal Object Names: This was seen to occur because of columns of the tables being given names that are a part of the Pervasive SQL 2000i Keyword list. I had noticed that we seemed to have tables/columns with the name ‘ACTION’, which was a keyword in PSQL. I believe ‘ACTION’ was not a keyword in your PSQL v7.0 release.
Record length inconsistencies: There seems to be an additional 1 byte that is being added to the field in the tables with 'Fixed Record Length mismatch’. It seems that PSQL 2000i has a new mechanism of tracking null fields. PSQL would add an additional byte for each null able field. Could this the reason for the ‘Record length inconsistencies’?
Table Files Don’t Exist: The DDF in the existing database seems to point to a data file (btr file) that does not exist!
Index Inconsistencies: The index inconsistencies that are being referred to here, I believe are linked to the ‘Index ACS Flag Inconsistency’ that is the most common crash in the Consistency tests.
General Dictionary inconsistencies: I haven’t looked into this part yet. Please pass on your comments on the same.

Our application here that uses the PSQL2000i backend is one that is used by many different clients (with separate databases) and our conversion from PSQLv7.0 to PSQL2000i resulted in problems all around. So we are looking for an approach that would be global. All we would like the users to be doing is to run a program that would synchronize the DDFs in their respective databases with the corresponding Btrieve files.
Following this deliberation, I had gone in for the SQL approach, wherein I would make a simple program to create a new database (that would contain empty DDFs by default) and subsequent to that I would be creating new tables in the database from the Btrieve files that would side-by-side update the DDFs in the database.

I would appreciate if you could answer the above questions and also validate my approach of creating/editing the DDFs to take care of the DDF-datafile failures in the Consistency tests...


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! Already a Member? Login

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