Information générale
Catégorie:
Gestionnaire d'écran & Écrans
>>Temp relationships by definition will force automatic pointer moving in related table/views, and this fact can trigger other things like row tableupdate()ing, bound controls refreshing etc. which might be unwanted or at least difficult to be forecasted/checked in real interface. <<
I'm not sure I follow the logic here, don't programmers use one to many types of forms all of the time?
>>So, if you want to move pointers correspondingly, then just keep programmatic links between table/views and issue SEEK/LOCATE when you really want to get pointer to new position. <<
If I understand you correctly, you're recommending that each time I change the record pointer in View 1, then I should SEEK the corresponding records in View 2. Hmmm... this doesn't seem such an elegant way to accomplish what a RELATION does automatically.
>>Actually, to SET RELATION in run-time, you should first index your views, i.e. it can be done in Form.Init event.<<
It would take too long to index fields in a 20,000 record tableview each time the form is opened. Can't I just set the "order by" in the view and then SET RELAT TO "orderbyfield" INTO tableview?
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