Solved

Paradox 5 Question

Posted on 1998-08-13
3
685 Views
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?
0
Comment
Question by:eriklee
3 Comments
 

Accepted Solution

by:
Marvman earned 60 total points
Comment Utility
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
 
LVL 1

Expert Comment

by:zircon
Comment Utility
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
 

Author Comment

by:eriklee
Comment Utility
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

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Introduction: I have seen many questions on EE and elsewhere, asking about how to find either gaps in lists of numbers (id field, usually) ranges of values or dates overlapping date ranges combined date ranges I thought it would be a good …
This article explains all about SQL Server Piecemeal Restore with examples in step by step manner.
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

728 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

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now