Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Referential integrity
Message
De
04/04/2006 11:54:25
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
À
04/04/2006 11:42:21
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01110216
Message ID:
01110304
Vues:
11
>Thanks for your solution.
>I thinked to this kind of work but I'm not sure if all the records will be copied correctly(mantain relationship), ...

As I said, you must copy parent tables before you copy child tables. adbobjects("relation") can help you get the relations. You can safely ignore relations with "ignore" in the third character (typically "RRI").

Another potential problem is triggers that update other tables, for example, update the current stock for reception/delivery of materials. In this case, an APPEND FROM will update the stock again! You must disable this through a variable which you enable before updating the database.

> I don't know what will happen if I'll remove some relations and add another.

The whole database should be copied to the new location, and then you do the APPEND FROM; with this process you will recover relations, stored procedures, views - in summary, everything that is defined at the database level.

>Must try.., and putting this in an automation process.
>Thanks again.
>
>Florin Groza
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform