Paradox and Referential Integrity is a Big Problem .. 
Author Message
 Paradox and Referential Integrity is a Big Problem ..

Hi,

There is a table that I couldn't open anymore a table,the message was
"Detail Table Open Operation Failed.", I tryed to repair the database
using the applicatinon FixIt, the solution that I use was to delete all
*.VAL files from my Database. I loose all referential integrity of my
database, but It works.

I tryed to copy "good" Table over the "Bad Table" but it didn't work.



Wed, 18 Jun 1902 08:00:00 GMT  
 Paradox and Referential Integrity is a Big Problem ..


Quote:

>There is a table that I couldn't open anymore a table,the message was
>"Detail Table Open Operation Failed.", I tryed to repair the database
>using the applicatinon FixIt, the solution that I use was to delete all
>*.VAL files from my Database. I loose all referential integrity of my
>database, but It works.

>I tryed to copy "good" Table over the "Bad Table" but it didn't work.

Create a new table, and 'borrow' the structure from your old table. Then add
the recorsd from the old tabel to the new one.

I agree with your subject line: these things are much too vulnerable. If one
file goes, so do many others. I now use procedural integrity only.
I also had a lot of trouble with directories of referenced tables being hard
coded (*but* I always used aliases), so I couldn't even transfer an app with
lookup tables to another machine.

Bye,
Jan

-----------------------------------------------------------------------

P.O. Box 697              2300 RA  Leiden            The Netherlands
-----------------------------------------------------------------------
** Specialists in multimedia software for education and presentation **
-----------------------------------------------------------------------
Usage of this email address for commercial purposes costs US$ 50 per
message. By using this email address you agree to this condition.
-----------------------------------------------------------------------



Wed, 18 Jun 1902 08:00:00 GMT  
 Paradox and Referential Integrity is a Big Problem ..


Quote:


>>There is a table that I couldn't open anymore a table,the message was
>>"Detail Table Open Operation Failed.", I tryed to repair the database
>>using the applicatinon FixIt, the solution that I use was to delete all
>>*.VAL files from my Database. I loose all referential integrity of my
>>database, but It works.

>>I tryed to copy "good" Table over the "Bad Table" but it didn't work.

>Create a new table, and 'borrow' the structure from your old table. Then add
>the recorsd from the old tabel to the new one.

>I agree with your subject line: these things are much too vulnerable. If one
>file goes, so do many others. I now use procedural integrity only.
>I also had a lot of trouble with directories of referenced tables being hard
>coded (*but* I always used aliases), so I couldn't even transfer an app with
>lookup tables to another machine.

There is actually an easy way to solve the problem.  I had been bit by
referential integrity several times until I found a rather simple solution.  I
found a utility on one of the Delphi sites (sorry I can't remember where or the
name, they are at work) that will generate the code to create a set of tables
including full referential integrity.  This was the key to solving the problem.

I use the generated code to build a entirely new database.  Then I use several
batch moves to move the data from the old database to the new database.  The
result is a program that will completely rebuild the database from scratch and
copy all the data.

This also allows me to build an empty database.  This is very useful if you ever
need to make changes in the linkage of a complex database with full referential
integrity between 40 or so tables.  If you have a lot of data in the tables it
can take hours to make a minor change.

There is one particularly {*filter*} bug with referential integrity in the BDE.
Never, I repeat never, give the referential integrity setup the same name as
either a field or an index.  If you do, the BDE gets confused and really weird
things happen.



Wed, 18 Jun 1902 08:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. Problem: Cascading Referential Integrity with Paradox tables

2. Problem Paradox x Referential Integrity x Network

3. Referential integrity on Paradox tables

4. Paradox, Referential Integrity, DbiDoRestructure, SQL

5. Paradox and referential integrity

6. Defining referential integrity in Paradox

7. Referential integrity in Paradox

8. Q: Referential integrity on Paradox database prevents delete

9. Using the BDE to add referential integrity to Paradox tables

10. Runtime creation of Paradox tables and Referential Integrity.

11. Does Delphi support Paradox REFERENTIAL INTEGRITY ?

12. Paradox tables and referential integrity

 

 
Powered by phpBB® Forum Software