Missing or broken reference to the file 'utility.mda'
Access 2007 Runtime program
I'm not sure if this is an appropriate question for this forum but I downloaded the 'Access 2007 Runtime' program from Microsoft's Download Center onto a PC which does not have Access.
I then installed one of my Access applications but when I try to run this application I get the following error message...
Your database or project contains a missing or broken reference to the file 'utility.mda'.
*To insure that your database or project works properly, you must fix this reference.
Loaded Access 2003 in Access 2010: Error missing reference
Loaded Access2003 file, and getting this msg: "Your Microsoft Access database contains a missing or broken reference to the file 'utility mode'. You must fix this reference"
Can't figure out HOW to fix this?
Reserved Error -1524 and Missing ref dao2535.tlb
A client called and said they had upgraded from Office 2007 to 2010 and to Windows 7. I only had a fews issues with forms at first. I was getting a message "Missing or broken VBE reference to the file 'dao2535.tlb" and a couple reports are giving me the Reserved error -1524 message. Another blog said to remove the reference to the dao2535, which I did. Now, when attempting to find the corruption in the one table, using an Append Query, the Conversion Error file stops with the following record. I'm not sure where to go from here. I can't find this reference in tools, now.
Conversion Errors1Object TypeObject NameError DescriptionDatabase
Missing or broken VBE reference to the file 'dao2535.tlb
Making .mda as Reference
What is the proper way to make a .mda? I use the following approach:
To protect the script I create a .mdb, then convert to .mde and just rename it to .mda.
Using this method, since there is no form in the start up of the .mdb, AllowBypassKey = False does not prevent user with Access to have a peek at the .mda to see what are the modules there is though the scripts are hidden since it is really a .mde
Missing utility.mda when trying to run an Access 2003 created db in Access 2007
I have an access db created in Access 2003. I am trying to run the db in Access 2007 and I receive an error message:
'C:\Data\Program Files\Microsft OFfice\OFFICE11\utility.mda' is not a valid path.
The Office 2003 install was a clean install on a new computer. Office 11 obviously relates to an Office 2003 install, which is the version of Access the db was built in.
As a result, bulit-in functions, such as TRIM, are not functioning.
Opening database : missing or broken reference to the file msado 15.dll version 6
I get the following error on one computer when I try to open the database:
'missing or broken reference to the file msado 15.dll version 6'.
Creating a broken reference
I'm trying to test the functionality of some code I wrote to check for broken reference code and fix it as required. How do I create a broken reference, simply deleting the file doesn't seemto be possible; I have to close access to delete the file and upon opening access the installer fixes it.
Missing or broken reference to the file OWC11.DLL
I have less the 10 people that use this database and not are in it at one time but just one person is getting this error message:
Your Microsoft Office Access database or project contains a missing or broken reference to the file" OWC11.DLL" version 1.1
she has been able to work in this last week and now this AM she is getting this message.
Access 2007 and Access 2010 database conversion errors
I am getting the following error message when I open a *.accdb database file in access 2007 and access 2010:
“Your MS Office Access Database contains a missing or broken reference to the file MSJETSQL.TLB version 3.0".
*To ensure that your database or project works properly, you must fix this reference.”
Opened the VBE Editor in MSAccess Menu -> References Found the reference marked missing . Removed the reference.
This did not work. I am getting following Error:
Object Type | Object Name | Error Description
Table | MSysACEs | -3831: The current file format no longer supports user-level security. The conversion or compaction process has removed any user-level permissions.
Database | Missing or broken VBE reference to the file 'MSJETSQL.TLB'.
error message about broken reference
I'm getting an error message which says 'your microsoft access database or project contains a missing or broken reference to file dao2535.tlb version 3.5, to ensure your database worksproperly, you must fix this reference.' If I click OK enough times I am still able to use the database but does anyone know how I can fix this?
Fixing Broken References
My app has a main FE mde which requires references set to two other FE mde files that are expected to be in a specific subfolder of the main FE path.
If the references are not initially set, or the path has changed, I have code that re-sets the references and life is good. But if I then close the app and intentionally"break" a reference by renaming a ...\subfolder\FE file, on start-up I immediately get a"...contains a missing or broken reference..." message before my check references code has achance to start.
I am using the Access 2010 runtime, so the app immediately shuts down after closing the message.
So, while a"missing" reference doesn't't seem to be an issue, I don't understand how you could ever fix a"broken" reference via start-up code if Access is goingto immediately squawk about it... Is there some way around this?
Missing or broken references
I am in the process of detailing procedures for migrating client databases from Access 2003 to Access 2010. While testing, I encountered 'Missing reference' errors. I was able to fix them by unchecking missing references. For instance, I have fixed a missing reference in Database A (on a shared network drive) in Access 2010 from my PC. Now, when a user opens Database A for the first time after installing Access 2010 on their PC, will they enocunter the missing reference error? I am trying to determine if it will be necessary to uncheck references at each PC
Access97 conversion to Access2010
When I converted an Access97 application to Access2007, there was a missing reference "Utility". I unchecked it and it seems to work well except the radio buttons. I have the IT to upgrade to Office2010 and I then converted the same application (which is in 2007) to Access2010. Now there is no missing reference, but it ceased to work. When I complied, it stucks on Date. I have tried all methods, such as linking to "Utility.ACCDA" and still wouldn't work. What am I missing? Is there anything wrong with upgrading from 2007 to
missing or broken reference to the file ꞌMSCAL.OCXꞌ
I have a database that works perfectly with 2000, 2003 and 2007 but when I try to open it on 2010 I get the following error message.
"Your Microsoft Office Access database or project contains a missing or broken reference to the file %uA78CMSCAL.OCX%uA78C."
Thanks to Allen Brown I had entered the following into my 2007 and earlier databases. Allan's web page is saying this should work in 2010
'Copyright: Allen Browne's Database And Training, 2007.
'Author: Allen Browne. [LINK]
* Note the 'IF' statement (in the client details form) has been entered by me to allow one calendar to update two text boxes.
If possible I would like to use the same coding for my 2007 and 2010 or later versions.
Broken Reference to MSCAL.OCX
I am planning a company wide upgrade to Office 2010 and I've found one database which has the following error while trying to run the DB
" You Microsoft Access database or project contains a missing or broken reference to the file 'MSCAL.OCX' version 7.0 "
I am opening this DB in Access 2010. I wonder if there is a safe and quick fix to this problem? (without the need of total overhaul of the DB)...
Broken reference to the file 'MSOUTL.OLB' version 9.2."
I have built a database using access 2007, using the Access 2003 mdb file format. My users have Access 2007 Runtime installed. Several of my users are getting the following error message when they try to open the database.
"Your CPMS database or project contains a missing or broken reference to the file 'MSOUTL.OLB' version 9.2."
When designing this database I included code automate sending emails when reports are ready. I included a reference to Microsoft Outlook object library 11, could this be the problem? It seems weird that I would only see the message now when I am trying to install updates.
The same program, with the same references have been workingon these computers for months.
Calling Form and Report in a .mda file
I would like to know that if it is possinle to call Forms and Reports which are in a .mda file.
0f it is possible is there a sample code which I can refere to
My PivotTable and Chart controls don't work in Access 2007
When you open a Microsoft Office Access 2003 or earlier Microsoft Access file format database in Access 2007, one of the following messages appears:
* Your Microsoft Office Access database or project contains a missing or broken reference to the file '0WC10.DLL' version 1.0.
* Your Microsoft Office Access database or project contains a missing or broken reference to the file '0WC11.DLL' version 1.0.
Access 2007 opens the database file, but any Microsoft Office PivotTable controls or Microsoft Office Chart controls that are contained on forms, reports, or data access pages do not work. In addition, Access might show the message "There is no object in this control" when you open an object that contains a PivotTable control or Chart control.
Broken reference when opening 2000 file in 2010
Got a new computer from my Company with Access 2010 on it. And when I open one of my databases (Access 2000) a window opens stating "Your Microsoft Access Database or project contains a missing or broken reference to the file 'MSCAL.OCX' version 7.0.
The problem appears to be with one of my reports. The first column contains a date field in which I entered the following format =Format$([When],"m y",0,0)
When I open the report on the old computer (Windows XP, Access 2007), it opens without the above warning. But when I open it in the new computer (Windows 7, Access 2010), I get the warning and the report shows the first column as #error.
Missing Libraries - Solution options
I have a question regarding how to handle missing libraries.
I converted an old Access '97 database application to 2003 but it does not work on PCs that only have the 2003 version installed because of a missing library. The library in question is "Microsoft DAO 2.5/3.5 Compatibility Library". I tried using "Microsoft DAO 3.6 Object Library" but no dice. If I manually add the library file to the correct folder, everything works. Although it works, I would rather not rely on someone remembering to add the file for new users/PCs. Is there not a way I could include them in the application itself?
I also just tried 2010 to see if that shows any improvement. It's even worse as it is missing yet another library reference called "utility.m4a" I think it was.
Any suggestions would be most appreciated! (it's been too long since I've worked in Access but it is starting to come back .slowly