Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Check for dupe ID...
Message
 
 
À
26/01/2001 11:11:36
Chuck Tripi
University of Wisconsin - Milwaukee
Milwaukee, Wisconsin, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00468745
Message ID:
00469270
Vues:
12
You are on the right track by wanting to put all data validation code in the database. This goes a long way to making applications independent of the front end [i.e., the UI].

>I created another form (idform) and it works much better. As long it works, it's fine, but is it something that I am not understanding why or what I was wrong about before (with Primary key, duplicated ids, etc)? As of now, it seems that I can finish up this project quicker, and then I will have to study the purpose of those indexes (Primary, Candidate, Unique and Regular). I know about Unique indexes, it is NEVER to be used (deleted records hidden kind of stuff).
>
>The MAIN problem with me is I want to do "everything" in the Database/Tables. Not that I don't want to do things in the forms, but if I need to use BROWSE, or anything else (around the form), I want to apply the same rules, so this is why I want to start "everything" in the Database/Tables. I am even using the record-level validation (calls a function) in one of the table already. I guess I need to make the Database/Tables "smaller" and the forms "bigger".
>
>Chuck
Mark McCasland
Midlothian, TX USA
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform