VAL file corrupt?! 1

[alvinmcg]

I have run into a serious problem and our IT folks (who do not like Paradox) have been unable to find a solution.

I have an "application" that includes 27 tables. Last week, there appears to have been some sort of network problem and now the master table VAL file has been corrupted. However, when IT restored an archive copy of this file, I continue to have the same problem.

I have considered simply recreating the validity checks, referential integrity, dependent tables. However, I can not recreate the referential integrity links. When I attempt to define the link, it will not allow me to save the change.

Please help. At this time we are dead in the water.

 

[Keys88]

When I run into this problem with Paradox 8 I delete the VAL file and the PX file. So far it has worked every time.

 

[footpad]

alvinmcg,

It sounds like you'll need to use Explorer (or a command prompt) to manually delete the supporting family files, e.g. .VAL, .PX, .X??, and .Y??.

You'll need to do this for the table in question, as well as for the tables that depend on these relationships. For example, if you're vusing problems with Customer and have defined RI to Orders, you'll need to do this for both tables.

Do *NOT* delete the .DB *or* the .MB files; otherwise, you'll lose data.

Once you've done this, you'll need to redefine the RI and validation checks.

For best results, *please* backup the data before doing anything.

Hope this helps...

-- Lance

P.S. Yes, this is a pain in the tailfeathers and is one of the reasons why the general wisdom says its best to handle RI through code.

P.P.S. This is also a good reason to keep printed documentation regarding the structure of your tables. That way, you don't have to guess at the number of indexes that need to be created.

 

[alvinmcg]

I ended up doing as suggested... Delete ALL *.VAL and *.X* and *.Y* files and then recreating the validity checks, and referential integrity.

The problem is gone and I am thrilled.