Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TURebuild Table: Version Mismatch 1

Status
Not open for further replies.

Fred40

Programmer
Nov 10, 2005
11
US
Friends:
I have made a grave error and request your assistance.
We are using Paradox Version 9.00.368.
On table repair I get these errors and the Table Repair cannot complete a repair.
1. Error Code: 45, Error Level: 1, Error Message: Secondary Index PART# does not match table.
2. Error Code: 32, Error Level: 2, Error Message: First record of Block 1 does not match index.

The problem started Monday due to my entry. In the table the field PART# is the key field. It had begun with the number 10001 up through row 46493. I foolishly named a blank record that we were trying to get rid of “10000” in edit mode. I cannot delete this record or rename it, and now my table needs repair according to Table Repair.

If I try to repair the table, I get a pop-up window entitled TURebuild Table with the message Version Mismatch. If I copy the table or the entire directory to another hard-drive, I can easily repair the table. I tried once to replace the table with errors with the one I repaired, but I think I remember it told me it could not open the table, and now I’m chicken to try again.

As you can see, these errors are totally my fault, and I should not have attempted to work with Paradox until I was more familiar with the software. To my relief however, the form, reports, and table continue to function without problems. I would like to fix my mistake if it is possible and restore the table. I have recently taken this job, and they call me a programmer (of which I am not, and did not hire on as, however I have been very successful with building and modifying MS Access programs for them). I have tried everything I can think of to repair this Paradox 9 Database; I had even immediately tried to restore with a previously backed up table, but was unsuccessful and now that table has been over-written.

Can you help me, or should I plan on a demotion to parking lot attendant or potato peeler?
Thanks
 
When you copy the table to another directory, and then successfully repair it, EXACTLY what steps are you taking to copy it?

If copying in Windows Explorer, are you copying just the .db file? If that is the case, that is why you are succeeding in that new location and not on the original. Paradox tables can have MANY files; .px, .xg*, .yg*, .fam, and many others.

If the above is the case, you may be able to recover that table completely.

Likely your best avenue will be to create a new table, and BORROW the structure (everything) of the damaged one. If you can do that, then you may be able to simply ADD the records from the original to the new one.






Tony McGuire
"It's not about having enough time. It's about priorities.
 
Tony,
Thanks so much for your help.
(To answer your question,when I copied the table, I copied the entire directory of tables to another drive using Windows Explorer. However, I am sure you are correct that there is a file or relationship somewhere that I must not have copied.)
I have studied up on BORROW and ADD and feel ready to create the new table as you suggested. However, I suppose I will have to give the new table a new name. Will the Form and Report work with the new table of a different name? Sorry to be so ignorant about this, but I'm not sure how the existing Form, Temp Table, and Report will work with my new table.
 
NO! The existing objects which use that table will NOT work automagically with a new table name.

You should, in my opinion, rename the existing table or copy it to a different directory. If copy, make sure you get rid of ALL of the database files (there are several extensions possible) before copying the new table to the directory where it needs to reside.

When copying the new table to the directory where you need it, use Paradox to copy it (Tools | Utilities | Copy). That way you get all of the right files for your version of Paradox.

Tony McGuire
"It's not about having enough time. It's about priorities.
 
Look at the Table Level...what level is it?

In the table repair utility it will tell you, as well as in the table restructure dialog, the window title.



Tony McGuire
"It's not about having enough time. It's about priorities.
 
I found this in reference to 'Version Mismatch':

================================
Have you run tutility (table repair) on this machine before? Did you upgrade the BDE from the one that came with P7? Basically, IDAPI32.DLL and TUTIL32.DLL need to match on the major version level (the number before the first .).

Search the HDD for all instances of the two files, check the
properties dialog, version tab, probably TUTIL32.DLL is older than the IDAPI32.DLL, in which case, go to the following URL and get the proper tutil version and replace all instances on the HDD.

================================

Tony McGuire
"It's not about having enough time. It's about priorities.
 
Wow,
Thanks for you continual interest in my problem.
I have checked both dll files as you recommended and the verisions match (Version 5.0.1.22). I have ran table rebuild on some of the Paradox tables in this system before.

Regarding levels, most of the tables in this system are Paradox 5. One of the tables that I have previously ran table rebuild on is a Paradox 5 and the table I am having trouble with is a Paradox 5. We are currently running Paradox 9. If you recommend, I will run table repair on another table to see if it will work there, (if the risk of possible bad consequences is low.)
p.s.
I still have not tried to repair by building a new table as you suggested due to my immediate priorities, but I certainly appreciate all the assistance you are giving. I want to be sure of what I am doing before I do something as drastic as creating a new table to replace the one with errors, so I will want to do that early in the morning before anyone signs on.
 
Paradox 5.

That's exactly why I asked.

The NAME of the table is likely too long for a Paradox 5 table.

Try copying it to a new name, 8.3 in size (test.db maybe?).

Then try the tutility again and see what happens.

Also, do you have table lookups defined? Those tables' name size could also be an issue; same thing.

In addition to JUST NAME, there are indications that the PATH TO THE TABLE could be too long. Same with a lookup table, if there is one.

Shorten the name and/or path, and/or upgrade the table to level 7.

MAKE CHANGES WITH COPIES!



Tony McGuire
"It's not about having enough time. It's about priorities.
 
The table with errors is named: WorkOrd.DB - Paradox 5
It has 2 lookup tables: Customer.DB - Paradox 4.x
and: Parts.DB - Paradox 4.x
Thanks again.
 
That is table name.

What about the PATH to those tables?

And since you have lookup tables, I become more and more suspicious.

I bet your issues go away if you upgrade ALL of those tables to level 7.

Make Copies First if you do the upgrade to Level 7.

Tony McGuire
"It's not about having enough time. It's about priorities.
 
I am not real clear about the PATH.
The Alias is :WORK: and Paradox 9 is located on the C drive and the tables, forms, and report files are all located on D drive in a folder named PD0XSVR and are available to the G drive for network access.
I am also not clear on how to upgrade the tables. Is there a program on the program installation CD? or is there a utility I'm not familiar with?
 
I found the info for upgrading the files on the Corel sight and will try this step.
Thanks, you have been extemely helpful and very gracious.
 
Tony,
My boss is considering permitting us to upgrade the tables versions 4.x and 5 in our Paradox 9 program to Paradox 9. (You had suggested version 7 but I don't know how to do that) I wanted to ask you if all we needed to do was to backup our system and then run the Update.ssl file? Will this upgrade the tables to version 9?
Thanks for all your previous help on this subject.
 
I don't know about update.ssl, but it is likely that it will change PROGRAMMATIC and GUI constructs to a current version (forms, reports, etc).

What you need to update is the table level.

I think a descending secondary index ups the table level to 7.


9 is the Paradox VERSION, not table LEVEL.



Tony McGuire
"It's not about having enough time. It's about priorities.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top