>some time back, i created a visual foxpro application containing a tree control (activeX) that requires file comctl32.ocx to be in the windows\system directory. no problem. later i installed visual basic. the same file existed with basic and overwrote foxpros comctl32.ocx file. my foxpro app no longer worked properly. i had to copy foxpros own comctl32.ocx file back. if i had written an app in both foxpro and basic that ended up on the same computer, how could this conflict been resolved?

The problem is not so much with the .OCX itself, it's more with the way its information is stored in your VCX. Say you developped your project with a '96 OCX and the production machine has the '97 OCX version, that's where you'll have the problem.

Doug Hennig came with an elegant solution to this problem in the June Foxtalk. Basically he instantiates the control at runtime rather than using it at development time. It's a must if you are serious about using OCX's.


José