Thank you very much - works great - only thing I had to change
was to move 'Public VBComp as VBComponent' from Option Explicit to
'dim VBComp as VBComponent' in the routines that used it.

Thanks again
--
Mike


"keepITcool" wrote:


your users may not have enabled "Access to VB project
setting in Macro/Security.

this will disable any calls related to vbaproject and it's properties.

on any normal install they WILL have extensibility dll on their
machines, so i doubt that is the real issue.

If other referenes are missing.. then you'll see
standard unqualified VBA methods e.g. Right("string",1 )misbehave.



--
keepITcool
| www.XLsupport.com | keepITcool chello nl | amsterdam


Mike Molyneaux wrote in


Is there a way to insure that the Visual Basic for Applications
Extensibility Library is available when Excel is started.

I'm using Excel 2003 on windows XP Pro with all current updates.

I have sheets that different users use & sometimes it's available &
sometimes not.

Thanks