Compile Error: Can’t Find project or library
Date() function quit working.
ACCESS97
It took me quite awhile to find all the information needed to solve this issue.
So I am repeating (plagiarizing) it all here to help the next person.
Got most of it from The_Doc_Man & Pat Hartman
This is a problem with references.
The problem is that everyone has individual copies of Access, each with potentially different registry data.
To fix the problem ON THE MACHINE WITH THE PROBLEM, click on OK and it should leave a Module window open with some function or procedure name highlighted. Doesn't matter whether it is a class module or a general module. Doesn't matter what name is highlighted. What it is telling you is that it couldn't find that entity when it tried to resolve all external references.
While still in the module window, from your menu bar click "Tools" then from the drop-down click "References." You'll get a dialogue box with a list and a couple of control buttons. One of the entries in the list presented to you will contain a check-box that is checked, but the name of the reference next to that box will be prefixed by MISSING: - that reference is your culprit.
When you identify the missing reference, look beneath the list-window to a gray rectangular box that should show you the file name it expects.
Click your start button (lower left corner) and do a Find of that name and type (but without the device or path). See if that file is on your system. If it is not, you are screwed. You might need to re-install Access with custom install to make sure all optional .DLLs are properly loaded to your miscreant computer.
If the file exists, jot down the path on a scrap of paper and close the Find dialogue box. Click Browse on the References box. Go back to the file path you copied. Double-click on the file. At that point, the browse box closes but I think the references box is still up. See if anything else is still checked but marked as MISSING.
If not, then close the References box. You should still be in the Module window. From your menu bar, click Debug then from the dropdown, select Compile All Modules.
If this works correctly, close your module window and go about your business. If it fails, you might have to repeat the process until all references are properly resolved as described above.
You can read up on references from the help file. Keyword is "references." The reason this happens is that you have to REGISTER every file you will use. There is a default set. But if you add a new feature to your database that uses a non-default reference source, the systems that share the database with you might not have set up that reference for you. And unfortunately, a reference is a database and registry mismatch caused by ongoing development of module code in a shared DB.
Now – my problem was references continued to stay grayed out or not show at all.
So……. you should open the db with the SHIFT key down. Then go to design of any module (or code behind any form) and press [Ctrl] [g]. Then go to Tools>>References and continue as mentioned above.
Read more at
http://members.rogers.com/douglas.j...enceErrors.html
http://members.rogers.com/douglas.j...enceErrors.html
Date() function quit working.
ACCESS97
It took me quite awhile to find all the information needed to solve this issue.
So I am repeating (plagiarizing) it all here to help the next person.
Got most of it from The_Doc_Man & Pat Hartman
This is a problem with references.
The problem is that everyone has individual copies of Access, each with potentially different registry data.
To fix the problem ON THE MACHINE WITH THE PROBLEM, click on OK and it should leave a Module window open with some function or procedure name highlighted. Doesn't matter whether it is a class module or a general module. Doesn't matter what name is highlighted. What it is telling you is that it couldn't find that entity when it tried to resolve all external references.
While still in the module window, from your menu bar click "Tools" then from the drop-down click "References." You'll get a dialogue box with a list and a couple of control buttons. One of the entries in the list presented to you will contain a check-box that is checked, but the name of the reference next to that box will be prefixed by MISSING: - that reference is your culprit.
When you identify the missing reference, look beneath the list-window to a gray rectangular box that should show you the file name it expects.
Click your start button (lower left corner) and do a Find of that name and type (but without the device or path). See if that file is on your system. If it is not, you are screwed. You might need to re-install Access with custom install to make sure all optional .DLLs are properly loaded to your miscreant computer.
If the file exists, jot down the path on a scrap of paper and close the Find dialogue box. Click Browse on the References box. Go back to the file path you copied. Double-click on the file. At that point, the browse box closes but I think the references box is still up. See if anything else is still checked but marked as MISSING.
If not, then close the References box. You should still be in the Module window. From your menu bar, click Debug then from the dropdown, select Compile All Modules.
If this works correctly, close your module window and go about your business. If it fails, you might have to repeat the process until all references are properly resolved as described above.
You can read up on references from the help file. Keyword is "references." The reason this happens is that you have to REGISTER every file you will use. There is a default set. But if you add a new feature to your database that uses a non-default reference source, the systems that share the database with you might not have set up that reference for you. And unfortunately, a reference is a database and registry mismatch caused by ongoing development of module code in a shared DB.
Now – my problem was references continued to stay grayed out or not show at all.
So……. you should open the db with the SHIFT key down. Then go to design of any module (or code behind any form) and press [Ctrl] [g]. Then go to Tools>>References and continue as mentioned above.
Read more at
http://members.rogers.com/douglas.j...enceErrors.html
http://members.rogers.com/douglas.j...enceErrors.html
