Erik,

Usually, a therm is created, updated and destroyed in the same proc/func. At least, this is what I do.

You can pass the object reference to another function that will be updating the therm

>Gregory,
>
>Ok. Thanks.
>But....
>
>I would like to access my progressbar in different procedures. Then it is not possible to do it like you suggest, or I have to pass the object handle to the function. :)
>... Did I just came up with a solution...
>
>Thanks!
>
>EriK
>
>
>>Eric,
>>
>>You can put the function wherever you like.
>>
>>Personally I have a Utlity.prg where I put many of the func/proc I use
>>
>>
>>>Yes, this is possible. But where do you store your function?
>>>I preffer to put in an different PRG...
>>>
>>>>Eric,
>>>>
>>>>something like this
>>>>
>>>>_Therm is a class and has a method Update()
>>>>
>>>>

>>>>use SomeTable
>>>>t = therm(reccount(), 'Processing..')
>>>>n = 0
>>>>scan all
>>>>    n = n + 1
>>>>    =t.Update()
>>>>endscan
>>>>release t
>>>>
>>>>*-------------
>>>>function	Therm(maxCount, Msg, MaxSeconds)
>>>>	return	CreateObject('_Therm', MaxCount, Msg, MaxSeconds)
>>>>endfunc
>>>>*---------------------------------------------------------------------------
>>>>

>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>I know how to create a simple progressbar using two shapes...
>>>>>
>>>>>However, I now want to put the progressbar in a class and access it in my appliction.
>>>>>
>>>>>I want to make default functions for it (i.e. acct_therm, upd_therm)... But how can I keep the object handle without making it a public property on my application object?
>>>>>
>>>>>Also, I don't want to create a public variable which holds the object handle.
>>>>>
>>>>>I would like to use anywhere i my app easy codes, like
>>>>>DO ACCT_THERM WITH "test1"
>>>>>or
>>>>>ACCT_THERM("test1")
>>>>>This activate the progressbar en sets the caption to "test1"
>>>>>
>>>>>and also
>>>>>DO UPD_THERM WITH 27
>>>>>or
>>>>>UPD_THERM(27)
>>>>>This updates the progressbar setting it on 27 percent
>>>>>
>>>>>How can I make functions/procedures public available (in two variants) without using an #include syntax and how to store the object handle??
>>>>>
>>>>>Can anyone help?
>>>>>
>>>>>Erik