Hello,
I have a PC which was recently upgraded from office XP to office 2003.
Now I am unable to use ACT or Quickbooks in conjunction with word 2003. It
appears this is related to VBA scripts being blocked. However, I cannot find
any reason why they would be blocked. Also this PC is running behind an SBS
2003 server, if this may be the issue. Lastly, I also cannot access the
Visual Basic Editor. Both trying to use ACT or Quickbooks as well as trying
to open Visual basic Editor gives me a very generic error stating that your
macro security settings should be set to High or lower. I have tried setting
the macro security to all settngs from Very High down to Low, which no
change. I have also forced the settings via a GPO policy on the SBS server
to make sure that VBA and macros are allowed. Your help is greatly
apreciated.

Re: How can I un-block Visual Basic Editor in MS Office 2003? by Shauna

Shauna
Sun Jul 02 17:57:45 CDT 2006

Hi Tim

Make sure that VBA was installed when Office 2003 was installed. Use the
Control Panel and Add/Remove Programs. Within Office, VBA is part of the
Shared Features.

Hope this helps.

Shauna Kelly. Microsoft MVP.
http://www.shaunakelly.com/word


"Tim Brogdon" <Tim Brogdon@discussions.microsoft.com> wrote in message
news:239ABF05-198C-4142-A41C-9A59FD44128E@microsoft.com...
> Hello,
> I have a PC which was recently upgraded from office XP to office 2003.
> Now I am unable to use ACT or Quickbooks in conjunction with word 2003.
> It
> appears this is related to VBA scripts being blocked. However, I cannot
> find
> any reason why they would be blocked. Also this PC is running behind an
> SBS
> 2003 server, if this may be the issue. Lastly, I also cannot access the
> Visual Basic Editor. Both trying to use ACT or Quickbooks as well as
> trying
> to open Visual basic Editor gives me a very generic error stating that
> your
> macro security settings should be set to High or lower. I have tried
> setting
> the macro security to all settngs from Very High down to Low, which no
> change. I have also forced the settings via a GPO policy on the SBS
> server
> to make sure that VBA and macros are allowed. Your help is greatly
> apreciated.