Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP triggers don't support buffering
Message
De
31/10/2001 06:40:45
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
À
31/10/2001 03:17:47
Eugene Kolmakov
Millennium Technologies
Vladivostok, Russie
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00575493
Message ID:
00575524
Vues:
18
>Does anybody knows the way to add triggers on buffered tables ? I've read in help that triggers don't support buffering and I just wonder why ? What I supposed to do when I want to add "Restrict" rule for deleting the key record from the parent table with matching keys in child one ? Use "Record rule" ? It's a procedure which is fired each time I edit record but I need to separate Insert, Update and Delete.
>
>P.S. I hardly can imagine working with large amounts of data via GUI without buffering data. So why shouldn't I use triggers to save my data referential integrity ? (This question is addressed to VFP developers team :-))

I use both together in my applications, all the time. I don't know any reason why you shouldn't combine triggers and buffering.

Please note when the trigger will fire:
use MyTable ...
CursorSetProp("Buffering", 5, ...)
replace MyField with MyValue && trigger doesn't fire
TableUpdate(...() && trigger fires here
Hilmar.
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
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform