Paradox 5 Question

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?
erikleeAsked:
Who is Participating?
 
MarvmanCommented:
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.  
0
 
zirconCommented:
Hi,

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!
0
 
erikleeAuthor Commented:
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.
0
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.

All Courses

From novice to tech pro — start learning today.