Hi Jay.

There is a really simple way to see what is invoking that procedure, and that is rename it and see what crashes :-) The debugger will pop up on the offending line of code, assuming that it's not in a property as I suggested before. If you don't like crashes then just activate the debugger in the procedure and check the stack. If that says that the offending line is the one that instantiates the object then I think that it fairly conclusive that it's a property causing the problem in which case you should open the class library as a table and look for your procedure name appearing in the Properties field. If the class contains any classes from other libraries then they should be checked too.

Ian Simcock.