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()).
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.