Can't add a reference to the specified file.

[Rdiamond]

I am working on converting an old Access 97 application so that it can work with Access 2013. I am able to convert the database file; the problem is that the original database had a customized add-in file (.mda). This add-in file includes functions and variables referenced in the application (I opened the .mda file in a text editor; I found the function and variable names mixed with lots of unreadable control characters). After converting the database, I cannot create a reference to the add-in file - it says 'Can't add a reference to the specified file.'
I have tried this using Access 2003, 2007 and 2013. I tried de-compiling, compact/repair and then compiling the application in Access 97 before converting; I also tried creating a new database in Access 2003 and then importing all the tables, queries, forms, and modules. Any assistance would be greatly appreciated!

[ItsMe]

...This add-in file includes functions and variables referenced in the application...

Why do you believe the references are to the MDA file? What is the name of the MDA file?

I am not pretending to know the solution to your problem. However, I understand this file to be a system file for Access. What I would do is use the Access 2003 wizard to import one or more of the objects from a copy (a Right Click Paste copy) of the original file. In the wizard, I would use the advanced options to "Import Saved Import Procedures" or something like that. I can't remember the exact words. So, what I am trying to say is, use the Wizard's advanced options to import Black Box stuff.

[June7]

Did you create the add-in and the mda file?

I have used only one 3rd-party add-in (Rick Fisher's Find and Replace). AFAIK, there is no mda/accda file involved as it is not application specific (I think that means a single database).

Review http://www.databasedev.co.uk/access-add-ins.html

[HiTechCoach]

cross posted here: http://www.access-programmers.co.uk/...=1#post1465438

[Rdiamond]

Why do you believe the references are to the MDA file? What is the name of the MDA file?...

What I would do is use the Access 2003 wizard to import one or more of the objects from a copy (a Right Click Paste copy) of the original file. In the wizard, I would use the advanced options to "Import Saved Procedures"...

Thanks! The MDA file (jdate8HOS.mda) was clearly shown in the references; importing the procedures from this file definitely helped.
There were several other issues I fixed - security, syntax errors, converting macros to VBA, etc.
So, now it works perfectly in Access 2007. However, when I try to open it in Access 2013, I get "error 2467, The expression you entered refers to an object that is closed or doesn't exist."

The error occurs on this line of code:

SH = Me.Subform0.Height / Me.Subform0.Form.Section(0).Height

Right below that is this line:

SW = Me.Subform0.Width / Me.Subform0.Form.Width

When I mouse over 'Me.Subform0.Width' (after the error), it shows 'Me.Subform0.Width = 8206'

Going back to Access 2007 (same database file, same directory), adding a breakpoint shows the same value for 'Me.Subform0.Width', and values for the other 3 properties:
Me.Subform0.Height = 5276, Me.Subform0.Form.Section(0).Height = 4755, and Me.Subform0.Form.Width = 10860.

So Access 2013 is doing something different in processing these lines, which causes the error. Any ideas how to fix?

[ItsMe]

I suspect the reason you are getting different values in different versions for the Height and Width is because the number of TWIPS are different on the two different computers. I do not see anything wrong with the code. The fact that you are getting values for the subform object's properties indicate there is not a problem with the subform missing or using an incorrect/misspelled name. So that leaves the variable SH. Again, I do not see an issue with assigning a value to SH.

Having said that, if a complex data type is missing code to instantiate it, you will have an issue assigning a value to it. Post the declaration of SH. Was it declared as a long integer? So I would also make sure the VBA code is 'Compiled' via the VBA editor's Debug>Compile Database. Make the determination of whether the error you are receiving is a compilation error or a run time exception.

Beyond all of that, you might have a corrupt subform control/container. I would, using Access 2013 and a copy of the Application, make note of the control source of the subform control and the name and delete the subform control. Then I would do a compact and repair. Then I would add a new subform control to the form. I would name the subform control something different than its previous name. Add the form object back to the new control's control source. Fix the VBA to reflect the new name of the subform control, do a Compile Database, save the project, and then a compact and repair. Then try running the app again.