ok.. first of all.. why not use set xxx as NEW xxx
form my point of view (and all that i read), if you do something like that you are adding overhead to your code, and can be very bad if you use that object a lot of times in your code...
every time you reference that object,
VB auto adds control code to see if that is the first time you reference it, and if it true then it load the class..
you will have something like this
if xxx is nothing then
set xxx = new xxx
but automatic by
VB...
i think your error is not starting the object.. maybe you miss the set xxx = new xxx at the start of your code??
Gonzalo Bianchi