We have ActiveX components written using VB SP2 running on NT Server SP4. All was well until we installed some new ActiveX components written using VB SP4.

All the components access MDBs, pull out information which is then sent across a network.

Now when any ActiveX is fired up we have a strange run pattern.

ActiveX works
ActiveX fails - runtime error
ActiveX works
ActiveX fails - runtime error
Etc...

It does not matter what combination of components are used, the pattern is always the same.

Any ideas?

Martin


[Edited by MartinBishop on 01-01-2001 at 04:07 PM]