Otherwise I would suggest you start debugging the VBA-code until you find what exact statement/call gives rise to this error. It must be some activeX or OLE-related statement, I think. Then try the general directions given in the error message like running that program before you call it, or reinstalling it.
Hope this helps, and let us know.
Kees

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic