Error trying view/edit VBA-modules of extracted global project (20

[Airat Araslanov]

I'm using Project Professional 2007 on the server, that's running the Project
Server 2007 (installed as stand-alone).

When I'm trying to "View code/view object" at module/form of extracted
global enterprise project in VBA Project Explorer, i'm getting an error -
"Error accessing file. Network connections may have been lost"

If I try to copy VBA module through orginizer, i'm getting the same error,
sometimes the Project even shutdowns.

Also, doesn't work view of "VBAProject Properties..." from context menu of
extracted enterprise global project.

Searched MSDN and some forums, but didn't found how to solve such a problem.
Tried to empty local cache in Project Professional and from cache folders in
Documents and Settings. Tried to check through other user accounts, the
problem doesn't solving.

I would be thanksfull if somebody could help me to solve that problem.
Any suggestion, that could help to restore normal functionality are welcome.

 

[Airat Araslanov]

Two more things, I want to add:

1. Problem appeared after some time of normal functioning, during which
editing VBA-modules worked fine.

2. Problem doesn't apply on other parts of Global Enterprise Project, like
Views and Tables, that are successfully editable through orginiser.

Also, sorry for my bad english.

 

[Dale Howard [MVP]]

Airat --

I would recommend you post this question in the
microsoft.public.project.developer newsgroup, as you are more likely to get
an answer in that group. Hope this helps.

 

[Mike Mahoney]

Airat --

I would recommend you post this question in the
microsoft.public.project.developer newsgroup, as you are more likely to get
an answer in that group. Hope this helps.



message








- Show quoted text -

Airat

I have logged this precise issue with Microsoft, unfortunately they
want to charge me for the time to investigate it. The way I recovered
from this situation was to restore the backup enterprise global. As
the the system only maintains one backup of the enterprise global it
may be this is corrupted as well. I had to go back and restore and
earlier version of of the archived database to find a working
enterprise global.

It is not clear to me what provokes the corruption which only affects
the running of macros or the ability of the VB editor to access the
enetrprise global. I speculated that it may have been caused by a
system administrator making a modification to the enterprise global
whilst her local MSP macro security setting was set to high - her pc
had just been rebuilt), however not been able to replicate the problem
so keeping my fingers crossed.

Good luck

Mike