Hi Zlatin
>< snip >
>>>So that if you need to capture your forms/datasessions you may need to redisign your app.
>>
>>Oh no. I've stopped using vars for global stuff. It is now all bound to _SCREEN.
>>I deal with a nice-to-have point in my error reporter, I will survive without.
>>
>>Thank you for your help
>>
>>Agnes
>
>I do not push you to use vars. This is if you wish to use ainstance() - it works also for arrays. But... as you wish <bg>

I clearly understand this. It wrote the lines above just for information. ::)
>
>What about creating your own class that will maintain datasessions objects? You can have a oDataSessions member object added to the _screen (if you preffer this instead of global variables) and with it you can handle all your datasession instances from a centralized place. You will have no more properties or containers that will have datasession objects in them. Instead your properties can contain identifier or some other data about the datasession object - so that you can retrieve a reference to it, when it is needed from the DataSessions maintainer object. Having all the instances in a centralized point may be advantage as for maintenance procedures.

That might be a way - but until now it will work without.
In the end I have some forms but I can scan forms with _SCREEN.FORMS. There is one single session object with a private datasession but this should not be the big problem. The use of session objects will be limited anyway so its no big deal.

I was just curious if there is an easy way to find the related objects for a session.
(I easaly can do this with a scan for the forms collection but I see no way for the sessions. The datasession window must get the information from somewhere so I looking around. ::) )


Agnes