Ahhh... Ok, my mistake. I thought they were sort of overridable like a normal constructor, but when I think about it logically, they can't be. I always assumed that unless you were doing something in the Initialize sub you didn't need to call it, but only Dim it. I guess what I should be doing is calling the actual constructor "Initialize" in my Initialize2 Sub (but is there a problem with that, can't access my computer at the moment to test, but I have a feeling I have tried that before). I do still need a sub that creates an instance of the class that remains blank.
Can you tell me why the code works when I step through it in the debugger, and not when I step over it? Very interested in this, even if the response is complicated.
Thanks so much for your help with this one Erel, I was pulling at hair I no longer have. The strange thing was that I just pulled the code from my B4A project, but I will have to look again to see if I did any refactoring and stuffed it up.
Cheers
Brian