I have an .exe application that uses several 3rd party ocx controls.  Every
now and then, the application locks up and uses 100% cpu.  I think one of
the OCX's is causing the problem.  Is there any way to tell which OCX (or
dll) is using all the cpu in a compiled exe?

Jon

You can add some type of tracing to your app to see when each control is
called/manipulated/other but it can get tedious. Addin's like CodeSMART can
do it for you. Also, this tool may pinpoint exactly where it's happening...
it's not cheap though. I can't recall "demo version" specifics but if the
apps small, the demo may work.

VB Watch Profiler, Protector, Debugger
http://www.aivosto.com/vbwatch.html

Input problem
Need to select MANY files for my app
OCX is not recognized.
Inputbox Question
NPer Function Error
Title bar
Oleaut32
Write Read to memory.
VB, SQL & Word
send mail