Bill,
Unfortunately, you must requery() the datasource.
In developing client/server apps I have always tried to keep a minimalist approach by giving the user a query screen that pulls up a few key fields worth of data.
The user selects the actual record they want to modify, delete, etc and a separate single record query is run based on the primary key of the record the user selected. This returns a single record cursor that is current at that time.
I have found that using a parameterized view works well for the editable record, and use spt (sequel pass through) for the read only navigation cursor.
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