No problem. There are any ways to handle this, but I think my object is "most value for the money". You can even use _screen to store the data, in which case not even a release all will remove your data!

Set PROCEDURE to fakturadata ADDITIVE 
_screen.AddProperty('data','')
_screen.data=CreateObject('parameterX')
_screen.data.aa='asda'
_screen.data.bb='asda'
?_screen.data.aa

>Thanks Tore.
>I like the way you handle the question.
>I was checking if Jim handles it in another way.
>
>
>>The object type which I describe in message#1364729.
>>
>>>Hi Jim!
>>>What kind of object?
>>>
>>>>My preference is to have a global object that has properties for all the global values that the system needs. I call that object the application object and it is usually named oApp and is the first thing created in the start up program.