Information générale
Catégorie:
Codage, syntaxe et commandes
Yes. That's what I do in forms that use a one-to-many relationship. Row buffering on the "one" table, and table buffering on the "many." Now that I'm trying to move to parameterized views...that changes of course. I probably oversimplify it, but I pretty much just ask myself does the user need to be able to cancel changes to more than record, or do they decide on one record (or row) at a time.
>Thanks for the response. If understand your response and Sylvain's I could have one table using row buffering and another related table using table buffering.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement