"File not found" in Visual Basic Editor

[ukb]

Hi

I have a problem in the Visual Basic Editor. I can hardly do anything
without getting the error message "File not found".

When I insert an object, be it a module, a form or a class and then try to
rename it in the Properties window, I get the error message. If I then try to
add some code to or remove the object, I get the error message.

Can someone help?

Thanks,
Ulrik

 

[Rod Gill]

Do you have any code in any other module that won't compile? Try selecting
Debug, Compile and fixing any errors.

If that doesn't work there ay be a corruption, so save the project into
another file format (.mpd for example) then re-open and save back.

Does this happen in all projects or just this one?

 

[ukb]

Hi Rod

Thanks for your quick reply.

I haven't got any code, yet, since I am never allowed to start coding. The
error also happens when I try to record a macro. When I stop recording, I get
the error message.

I have tried both of your suggestions, I have tried to repair the
installation and I have tried to create a new project but I still get the
error.

According to the help system it is an error 53 meaning one of 3 things:

1. A statement refers to a file that does not exist ( I haven't coded, yet).
2. There is a call to a procedure in a DLL that can't be found ( I haven't
coded, yet).
3. You try to open a project or a text file that doesn't exist (it does).

Any suggestions?

Thanks,
Ulrik



In the development environment, this error occurs if you attempt to open a
project or load a text file that doesn't exist.
Check the spelling of the project name or file name and the path
specification"

 

[Rod Gill]

Press Alt+F11 to open the Visual Basic Editor
Select Tools, Reference

See if any of the checked options at the top of the list has MISSING
displayed in the description area below. If so, deselect that reference and
try compiling again.

 

[chakrat]

Hi Ulrik,

You can try the following:

Save mpp file into .xml format. Then save xml version back to mpp. I
hope xml version will be clear all these kind of error.

Thanks
Chak

 

[ukb]

Hi Rod

Thanks for your reply.

I looked in the reference as suggested and it all looked fine. All the
checked options had a path in the description area and I checked to make sure
that the files pointed to existed.

Besides this, I tried to create a macro in MS Excel to see if I had a
general Visual Basic problem on my machine. I could create macros in here
without any problems, so I guess this is not the case.

Any further suggestions are most welcome!

Thanks,
Ulrik

 

[ukb]

Hi Chak

Thanks for your reply!

I tried the idea of exporting as XML and then open the xml file as a normal
project. It did not have any effect on the error.

Please let me know, if you have any further suggestions.

Thanks,
Ulrik

 

[chakrat]

Hi Ulrik,

We got a same problem and I cleared the error. You need to import XML
file as new project. I hope you did the following:

1) Tools -> Enterprise Options -> Import project to Enterprise

2) Choose XML file and by selecting XML file as file type

This action will be create the new project, so delete the old project
plan which is giving the error.

Thanks
Chak

 

[chakrat]

Hi Ulrik,

We got the same kind of problem, so I did the same.

After you exporting the mpp file as XML, then you need to import XML
file as MPP.

steps:

Tools -> Enterprise Options ->Import project to enterprise

Choose XML file by selecting XML as File Type)

This action wll be save the XML file as new project.

Delete the old project plan which is giving error.

I hope this will work.

Thanks
Chak

 

[Krishna Alavala]

Hi Ulrik

You need to delte your cached global.mpt file present in the following
directory
C:\Documents and Settings\<User>\Application Data\Microsoft\MS
Project\11\1033. This file will be create as sson as access Project Pro 2003.

Let me know if this works or not.

Thanks
Krishna

 

[G Lykos]

Greetings, Chak.

This is to ask if you had any success in resolving this problem. By the
way, you'll notice in the VBA IDE (once you get past the diagnostic
messages) that the node for the project file is missing in Navigator. This
corruption is reported periodically, and the MVPs monitoring this news group
don't seem to remember past occurrences and suggest trying the same things
which don't help.

The only (painful) solution we found was to copy all schedule information
(which is accessible, except for any VBA code you might have had in the
schedule rather than in Global) over to a new project.

It appears that the origin of the problem may be related to links. Out of
curiosity, did you have any links (schedule to schedule predecessors, or
paste value-text from Excel, etc.) now or before in the file where you
experienced this problem?

Regards,
George

 

[Chak]

Hi G Lykos,

My project plan doesn't have any links prior/after this issue.

Good Luck!

Thanks
Chak

 

[Chak]

Hi G Lykos,

My project plan doesn't have any links prior/after this issue.

Good Luck!

Thanks
Chak