Fixing a File Not Found error

[roadkill]

I have an MS Project file that seems to have something missing that is
causing File Not Found errors. They seem to pop up whenever this file is
open in MSP and MSP is checking for any macros (e.g. when the file is loaded,
when the modules tab is clicked in the organizer, when an attempt is made to
move a macro to the file via the organizer, etc.). No modules show as
present in the file and none can be added using the organizer. Also, I can't
create a macro in this file (not even by recording - if I try I get a message
saying the macro name is invalid regardless of what I try to use for a macro
name). It would appear that wherever is supposed to be in this file that
tells MSP where macros should go or would be is missing. Any ideas on how to
fix this?

 

[RTucker]

Roadkill,

I experienced this same problem. For some reason unknown to me, the VBA
hooks in the mpp file are gone. The Test:
T1- Create and save a new schedule file, open the VBA Editor and you can
view the current project filename in the VBA Explorer frame on the left.)
T2- Open the problem file and go to the VBA Editor. The filename is not
there. Yes? It's corrupt!

Solution:
You need to Export your data out of the bad file into XML format, then
import it to regain the VBA hooks in the mpp file.
S1- Perform a Save As... with the problem file. Select XML as the File Type.
S2- Close all project files using CTL-F4, leaving MS Project active with no
open project files.
S3 - Perform a File / Open..., select the XML filetype and open the XML file
from Step S1. This will import the data values from each task, resource,
association, etc. into a new mpp file. :>) (I wrote the above text w.o
confirming these steps, but they should be very close to accurate.)

The issue I had when I did this was that the bad mpp file was 30MB, and the
XML created was 335MB. That's a 335MB text file! A four processor 3GB-RAM
workhorse cound not open/import the XML data.

Solution B -
B1 -Open a new project file. Set up ALL the Tools-Options and Project
Properties identical to the bad file
B2 -Insert a project at Task Line 1. Select the bad mpp file.
B3 -Select the inserted project at Task Line 1, open task properties, go to
the Advanced Tab.
B4- Deleselect the "linked" checkbox. This will import all the data into
the new file.
The drawback to this method is that the Unique IDs for all tasks are
renumbered. My project depends on UIDs for contractual issues. The
workaround is to copy the UID to an available Text field before unlinking.

BOL,

RTucker, PMP