Information générale
Catégorie:
Gestionnaire d'écran & Écrans
Dear Vlad,
I have seen the light... lol... Now I see what you mean. By making it (the methods) a class object vice form method the integrity is assured. While I now have some 'reconstruction' to do I can see a huge benefit. Thanks!!!
Ric
>Hi!
>
>Right. Once I used that approach, and was quickly frustrated by constant requirement of that parameter (data session) that I usually forget to pass (and then spend a lot of time to figure out that I just forget to pass data session ID as parameter).
>
>
>>Hi Vlad,
>>
>>PMFJI on my own thread... That's exactly what I did and it works great. I thought the 2nd option sounded like it could mess with stuff too much.
>>
>>Renoir
>>
>>>Hi!
>>>
>>>It is dangerous to work with SET DATASESSION command inside of the form. for example, grid might be reconstructed when you do so. I meant:
>>>
>>>- Make a class (say, clsDataHandler), put data refreshing and saving methods there. Base it in the Custom VFP class.
>>>- Make a base class for all your forms that work with data. Add clsDataHandler class to the base form class as object.
>>>- In the form code when you work with data, instead of call to public object you call the form object (instead of oApp.Save(), for example, call thisform.oDataHandler.Save()).
Précédent
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