CFObject has always been fairly well limited in the range of COM
interactions it handles. We learned the hard way. Esp bad if it's a 3rd
party COM object you can't modify.
We got around it by inserting a VB5 "shim" between CFOBJECT and the OCX it
couldn't talk to. CFOBJECT called the shim, the shim called the OCX.
CFOBJECT was broken in 3.x, and still broken in 4.0, don't know about 4.51.
Len
=============
><CFObject> has been around at least since version 3.0
>
>--Jeffrey
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
