>I have the impression that the 'error' in question is a catch-all for several errors, not all of them memory address related. For example, I have a repeatable error with grids that have their control source done programmatically and another with two tables with identical field names. The DCOM error is also repeatable, etc. etc. I'd REALLY like to see an 'honest' error message - then I can correct the problem in my code.
>
>My $.02 US.
>
I agree wholeheartedly. Unfortunately, with ActiveX controls, it may not be possible, and that may be the reason for the C...5 error message. The actual sequence was I'd get a syntax error doing CREATEOBJECT(), try to fix it, re-try CREATEOBJECT() and bang. The only change I made was to remarking out the reference to the procedure where the imagelist was sub-classed, and replace the name of the sub-class with "OLECONTROL". Then, no syntax error no C...5 errors (I hate counting zeros< g >).