>Hi Frank.
>
>>Thanks Doug, I was pretty sure it was you who had posted about this, but couldn't find the article when I searched on your blog. I'll see if I can work it through later today. As this involves programs not under my control, is there any way for me to tell what activex is being used that is causing the problem?
>
>Not AFAIK. It'll probably have to be trial and error on all of the OCXs your app uses.

That's a bummer as the applications giving the problem are not my apps. I wonder if Process Monitor or something like that might help.