If the App has a common subclass of each control, you might add logging identityy info in gotfocus / lostfocus.
If not, you might try to hack some Eventbinding to ActiveForm / ActiveControl and Log from there.
If you are lazy and patient, you might try to set coverage log and check the last entries before the crash ;-)))

HTH

thomas


>>>Hi,
>>>Error 1152 = "Cannot access selected table"etc usualy is caused when the select statement of one of your combo or list boxes is incorrect.
>>>It shows that this error is not caught with a usual errorcatcher like e.g.
>>>ON ERROR DO ERRORLOGGING WITH ;
>>> ERROR( ), MESSAGE( ), MESSAGE(1), PROGRAM( ), LINENO( ), SYS(0), ALIAS()
>>>
>>>I am now working on a legacy application where I face this error and I cannot find which object is causing error(1152) any way how to find out instead of checking all the comboboxes (> 100) in the application?
>>>
>>>Regards,
>>>
>>>Koen
>>
>>Can you find which form is causing the problem?
>Naomi,
>no I cant find which form, which combobox is causing this.
>There are several forms and multilple comboxes involved, that's why I was looking for a possibility to have this error caught by my errorlogging() - it seems the default error() is not activated on error(1152)
>Rgds,
>Koen