Sometimes users seem to get this error when automating MS Office applications. I've created VB wrapper classes that perform different functions over their related office objects (eg - cWord, creates an instance of word once initialised, allows access to the Word.Application object, has a few generic routines, destroys object on Class_Terminate).

Can anyone suggest any ways to avoid this issue, I'm not totally clear on the circumstances that can create the error.