Hi

Unfortunately no - I'm still developing that product on a knackered old NT4 workstation

So far as I know it is someting to do with the 'user' that is running the dll in the vb ide versus the 'user' that is running the compiled com+ object on XP/W2K (ide fails in XP, but compiled works. Both compiled and ide work ok on NT4). I have been told by developers at my company with many more years experience than myself that there is no way around this and they all use NT4 too, but I can't believe that! There has to be a way around. There are some MS knowledge base articles skirting around this area that involve adding some registry stuff, but I have not been able to get any of it to work yet (and nearly killed my XP PC in the process!).

Sorry for the negative response. If you have any luck yourself, please let me know - I can't stand developing on NT4!

Cheers