VBA ERROR LOADING PROJECT ON WINDOWS 2000

VBA ERROR LOADING PROJECT ON WINDOWS 2000

Anonymous
Not applicable
293 Views
6 Replies
Message 1 of 7

VBA ERROR LOADING PROJECT ON WINDOWS 2000

Anonymous
Not applicable
AKOs, When I select Tools|Macro|VBA Manager and select New; On NT 4.0 service pack 6, PCs VBA loads a new project or existing project just fine. On Windows 2000 pro, I get an "Error loading project" if I am not logged in as local admin, so for most of our users, it's not working. I figure it's a permissions issue in the registry. What are the registery keys that need to be changed to allow a user to load a VBA project or create a new one? Any ideas? Tim
0 Likes
294 Views
6 Replies
Replies (6)
Message 2 of 7

Anonymous
Not applicable
nobody knows?
0 Likes
Message 3 of 7

Anonymous
Not applicable
 

Are they Power Users? They have to have at least
those rights, or Admin.


--
--
Ed
--


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
nobody
knows?
0 Likes
Message 4 of 7

Anonymous
Not applicable
They are not in the Power Users Group. We have found the registery keys that allows AutoCad 2000 to work for a regular user. We are looking for those keys in the registry that will unlock the VBA too. Our IT group does not want users in the Power Users Group....There are holes in the security...

Tim
0 Likes
Message 5 of 7

Anonymous
Not applicable
Can't help you there. Sorry.


--
--
Ed
--


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
They
are not in the Power Users Group. We have found the registery keys that allows
AutoCad 2000 to work for a regular user. We are looking for those keys in the
registry that will unlock the VBA too. Our IT group does not want users in the
Power Users Group....There are holes in the security...

Tim

0 Likes
Message 6 of 7

Anonymous
Not applicable
Well that is probably your problem. It is a *requirement* that users are
power users with 2000. Try changing a couple of them to power user and
see if the issue resolves itself. If it does, you have two options -
grant them the rights or upgrade to 2004 [which doesn't require power
user rights]. Not much help, but until your environment meets the
minimum software requirements, there is not much we can do to help.
___________________________
Mike Tuersley
AutoCAD Clinic
Rand IMAGINiT Technologies
0 Likes
Message 7 of 7

Anonymous
Not applicable
Actually it is not a 'requirement' but a convenience....
We have found the registry keys that allow a regular user the ability to run A2k without giving away the farm. We are close to knowing what the VBA keys too. I had thought that someone on this site would have found this already...sorry if I assumed too much.....I know that AutoDesk knows, but they will probably not tell....unsupported you know.....:)

Thnx...Tim
0 Likes