help winth MISSING reference

Question

regards.
I need help.
I was getting an error on references in the VBA editor, I read a page that suggested that a workaround for this problem was to enter the VBAeditor to disable the option in tools -References -MISSING.
I did and nowI get another error.
says as well as in the image

and what is worse I re-enable the checbox of Missing but not find it.

Answer 1

Hi, when a reference is missing, you need to set it to "checked". Navigate to the VBE then TOOLS then REFERENCES then check the missing item(s).

If the missing item is not available, then your system is missing a file it needs, like a dll or other file type. There is no way for me to tell you what file you need since I have no idea what you are trying to do. Research some of the code keywords you are using and look for associated file libraries that are required.

HTH

Answer 2

Hi Augusto,

Welcome to the MSDN forum!

Please show us the code you use and point out the line when the error message come. Debug the code please. 

Or, as HTH has mentioned, you can search the internet based on some key word in your code and try to find the proper library. 

Thanks.

---

Yoyo Jiang[MSFT]
MSDN Community Support | Feedback to us

Answer 3

I have found that this problem usually occurs when the workbook is opened in an Office version earlier than the one in which it was created. In the References you will see Missing........ etc.

Note the name of the missing reference and then uncheck the box against it and then scroll down in the references and find the equivalent reference in the version of the application that you are using and check the box against that one. Basically it is a backwards compatibility issue because the earlier version does not recognise the reference for the later version. Forward compatibility (ie older version to newer version) does not seem to have the same problems.

When I say opened in an earlier version than that in which it was created, you can create code in an earlier version and move the project backwards and forwards between a later version and earlier version and still OK. However, if the VBA code is edited, it inherits the version in which it was edited so if this is done in the later version then as soon as it is taken to the earlier version the problem occurs.

Depending on what the references are, you may be able to eliminate the probems by using late binding. Google Late Binding and Early binding if you want more information on these.

I usually use Early Binding with the references when developing because the intellisence kicks in and helps with the editing of the code. When the project is working, I edit the code and revert to Late Binding to eliminate problems between the versions.

---

Regards, OssieMac

Answer 4

Regards.
Thank you all for your responses.
I think the problem was that ddI was not properly referenced in the path.
It showed the path something like
C:\ProgramFiles (x86)\.....
which I thinkis a route of 64-bit windows
from which came the file,

I work on Windows32-bit and I don't have that folder on my pc.

Could this be the problem?

Answer 5

Regards.
Thank you all for your responses.
I think the problem was that ddI was not properly referenced in the path.
It showed the path something like
C:\ProgramFiles (x86)\.....
which I thinkis a route of 64-bit windows
from which came the file,

I work on Windows32-bit and I don't have that folder on my pc.

Could this be the problem?

Did you go through the process I gave you and remove the missing reference and then find the equiavlent reference and check the box against that one. If you did then it should work. The problem created is similar to moving between earlier and later versions of Office.

I am assuming that you are calling one application from another application. Is this correct? If so, post the code where you are doing this and it might be possible to change the code into late binding so that the references are not needed.

---

Regards, OssieMac

Answer 6

Thank you OssieMac.
Your reply helped me a lot.