Paradox 5 Question

Posted on 1998-08-13
Medium Priority
Last Modified: 2008-02-01
let me start by saying i dunno much about Paradox Dbs...

i been given 6 paradox files - issues.db, issues.px, issues.yg0, issues.yg1, issues.xg0, issues.xg1
i only work with ODBC drivers (Microsoft Paradox ODBC driver is the general jet engine odbcjt32.dll Nov1997) and browse via Borland_BDE.

[1] ODBC spits an error msg saying "External table isn't in the expected format"
      i have tried both collating sequence - ASCII and International..
[2] DBE/DB_Explorer says "Invalid table name" when i tried to browse the actual data or look at the field names.

Any ideas, forumers?
Question by:eriklee

Accepted Solution

Marvman earned 240 total points
ID: 1025547
Paradox creates the additional files to the original table issues.db when referential integrity and validity checking are turned on in Paradox.  There are 3 Possibilities to check

1.Either your ODBC connection is not setup correctly or wrong driver is being used.  In this case you would not be able to connect to any of the tables in this database.

2.The table is corrupted.

3.The other tables the referential integrity are referring to are missing or their links are not valid.

If you have been accessing other tables in this database then your driver is okay.  If you have access to Paradox open the table and make sure it is not corrupted and that it is not password protected.  

Expert Comment

ID: 1025548

FYI - all of the files you were given relate to a single table that contains data:  issues.db.

All of the other files relate to properties of that table.  For example, issues.px contains information on the primary key and indexes of the issues.db table.

I believe Marvman is probably on the right track with regard to solving your problem(s).

Good luck!

Author Comment

ID: 1025549
thanks for all forumers' contribution. Marvman got me moving..i installed Paradox7 just to examine the database.. found it was version 5. Checked my ODBC drivers -I thought i had used 5 but was actually version 4.0. Wow, version 4 and 5 are not compatible. The problem was exacerbated by the fact they were too many different dbs of diff version from 4 to 7.  Anyway everything ok now & i can access via ODBC.

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Blockchain technology enhances society similar to the Internet. Its effects are broad, disruptive, and will boost global productivity.
A method of moving multiple mailboxes (in bulk) to another database in an Exchange 2010/2013/2016 environment...
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

597 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