>>>Hello everybody.
>>>
>>>in my app i've found a wired behaviour. Vfp seems to foreget every now and then that a certain method exist in a specific object. the line

>>>oToolBox.oAppSupport.ErrLog_Manual("Printer Install-" + ErrMsg, DataStr)

>>>sometimes triggers an error

>>>Property ERRLOG_MANUAL is not found.

>>>well - its there, and a few minutes later (without restarting the app) vfp knows its there and executes this command correctly. i've seen this behavior with other methods as well.
>>>
>>>does anyone have an idea how this could happend and what to do about it?
>>>
>>>thanks in advance to everybody!
>>
>>Gunnar,
>>When it happens, oAppSupport does really reference an object that has that method?
>>Cetin
>
>hello Cetin
>
>thanks for your reply
>
>yes, it has to be. oToolBox is a custom class with only properties (with access method) the access for oAppSupport looks as follows:

>IF UPPER(PROGRAM(PROGRAM(-1)-1)) <> "TOOLBOX.DESTROY"
>	IF TYPE("THIS.oAppSupport") <> "O" .OR. ISNULL(THIS.oAppSupport)
>		* *** THIS.oAppSupport = NEWOBJECT("AppSupport", _SCREEN.LocalMainPath +"classes\"+ JUSTFNAME(THIS.CLASSLIBRARY))
>		* *** the above  should be a bit faster (because no search in folders)
>		* *** but for some reason it sometimes triggers the following error:
>		* *** "m:\mm\classes\functions.vct is not an object file."
>		* *** so, we're gonna do it the slow way
>		THIS.oAppSupport = NEWOBJECT("AppSupport", THIS.CLASSLIBRARY)
>	ENDIF
>	THIS.AssignCaller(THIS.oAppSupport)
>ENDIF
>RETURN THIS.oAppSupport

Gunnar,
I'd double check with pemstatus, amembers, debugger etc. I don't use access often for it calls assign.
Cetin