Suggest for fixing bug

[Mocha]

Dear Microsoft,
I've got error "Error accessing file. Network connection may have been lost"
when i work with VBA in Ms Project Profesional 2007.
Could microsoft publish the service pack for fixing this bug cause i rode
many article that it was bug in office product but i could find the solution
and service pack for Ms Project Profesional 2007
Thank you very much

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...a595a9f&dg=microsoft.public.project.developer

 

[Harry.A.I]

I have had the identical problem and I think I now know what the root cause
may be, but the possible solution is elusive. We have Project Server 2007
and managers using Project Professional 2007. On the Project Server is a
project file that contains significant VBA code to include code in the This
Project.Project.Open (I believe this to be involved in the problem). The
user, which has macro security set to Medium, selects disable macros since
they will not use the file’s code. They save the file back up to the Project
Server. The next time the user checks out the file, enables the macros, but
the VBA generated buttons do not appear. Open up the VBA and try to open any
of the modules or forms and the following message appears: “Error Accessing
File. Network Connection may have been lost.†The VBA code is inaccessible
and seems to be corrupted.

In doing research I’ve come to this conclusion on the errant file(s). The
VBA code has had a compile problem. Now mind you this is speculation based
on what information I’ve gathered and the circumstances surrounding the
problem. I’ve seen a number of postings about VBA errors similar to this
with the Project Open event coupled with the user’s disabling of Macros (on
Medium security) seems to cause the project open to start to work (compiling
for use) and then the remainder of the code remaining decompiled (due to the
disabling of macros). This leaves the code compile in a sort of mid-state
compile (there are a number of stages VBA goes through for compiling- I’ve
read between 7 and 12 depending on source). The user then saves the file
back to the Project Server thus preserving this erroneous VBA state.

Why did come to this conclusion? MS-Access had the identical error message
when a similar (but not identical) situation arose. I don’t believe in
coincidences in code especially when the error message is identical and is
probably called from the same core code and as a result of a similar problem.
Fortunately for Access users they have the /decompile switch which allows
them to decompile their code and then to recompile it thus saving their code
and their file. Only Access has this decompile switch, no other Office
program does.

I may be off base, but I don’t think so. I would request a fix to prevent
what seems to be a VBA compile issue on file open and the ability to have a
decompile switch to deal with situations like this.

Thanks you,
Harry Irvine

 

[Taffy]

"Click I Agree in message pane" they say.
I would if I could find it!!

I need a solution to this problem now and I am dissapointed that Mocha, who
raised this issue on 31st July, still hasn't received a 'fix'.

I believe it has something to do with using VBA code created in MS 2002 and
then moved to, and used in, MSP 2007.

It is now November and time is running out for me as my clients are moving
from MSProject 2002 to MSProject 2007 in January / February next year.

 

[Mike Mahoney]

"Click I Agree in message pane" they say.
I would if I could find it!!

I need a solution to this problem now and I am dissapointed that Mocha, who
raised this issue on 31st July, still hasn't received a 'fix'.

I believe it has something to do with using VBA code created in MS 2002 and
then moved to, and used in, MSP 2007.

It is now November and time is running out for me as my clients are moving
from MSProject 2002 to MSProject 2007 in January / February next year.







- Show quoted text -

Harry

I have just hit this problem with MSP 2007 connected to Project
Server. I have several instances of project server containing a macro
in the enterprise global. Opening MSP and connecting to server A -
macro works as specified; closing MSP and re-open to connect to server
B - macro no longer functions and cannot open VB editor because of
error accessing file message. Previous to this one of the project
server administators had made changes to the enterprise global on
server B when the macro security setting on her MSP was set to high.

No solution though. I will investigate restoring the enterprise gobal
from archive.

regards

Mike

 

[AndreyZ]

I've the same issue....

How to restore only EGlobal from archive?

Thanks,
AZ

:

.....

 

[AnthemAZ]

I've read all the posts for the Error accessing file. Network connection may
have been lost.

However, it's now 2010 and these posts are dated 2007 and 2008.

Does anyone know if there is a fix?

We are converting to Office 07 and Project 07. Some already have and some
are still on Office 03 and Project 03.

We keep getting this error message when accessing files.

Thanks for any advise.

AnthemAz

 

[Barbara - Austria]

Hi AnthemAz,

I wish I knew of a fix. If someone knows I am quite interested to read
about it.

I was 2009 involved in at least two discussions but I am also not able
to find them. I had a support call for that, but MS could not help. They
only told me how to correct what I had already known (see below).

I still don't know what's causing that. I have even seen that with
projects without any macros in there.

As mentioned, I don't know how to avoid, but there is way to repair:
Save your project plan as XML. Open this XML with Project. A wizzard
will start to create a new project plan.
One constraint: If you are using Project Server with Timesheets, link
for tasks between projects and timesheets (e.g. in cube
MSP_Project_Timesheet or reports) will be lost since tasks will get a
new TaskUID.

Hopefully someone else can give us a tipp for a fix ...

Regards
Barbara

Am 24.02.2010 18:51, schrieb AnthemAZ: