You really need to do some error tracing. There are many different ways to 
trace errors. I do it by building a stack list on the way back up. A 
common way to do this is to add each layer to the err.source with a 
delimiter. I use a pipe (|). I will even put all non-object parameters in 
so I have an idea of what data it was failing with.

Then have a way to log the error source when you get back to the user 
interaction level (like a user initiated event). In a library (OCX/DLL) I 
will log when I get to a public method/property, and still raise it. This 
ends up logging the error multiple times (once for each library it goes 
through, and once for the exe), but I find it is a little easier to trace 
smaller stacks.

There are many other ways to do error tracing. Another way is to log each 
statement to a file. That way you can trace exactly what is being called. 
This is a little extream, but I have done it before when I have found the 
procedure, but the line of code isn't obvious.

If you don't want to do all that work. The first place I would look at is 
the Class_Initialize for all the classes you are calling.


John. 

> No I dont and that is why even myself is confused about it.

Bharat Saboo