Compile error when moving application to lesser version of access

[WAVP375]

An application developed on windows 10 current version of access runs beautifully. When moved to the production environment when executing the following code I get a compile error 'Can't find project or Library' and the error highlights the word Right in the line of code. When checking the reference list it show 'Missing Microsoft Access 16 Object library'. That library is not listed in the list obviously. Is ther way of coding around this or can the missing library be loaded somehow?

Any thoughts will help significantly



Private Sub BtnDisplay_Click()

Dim LResult As String
LResult = Right(ImagePath, 1)
If LResult = "f" Then


GoTo PdfDisplay
ElseIf LResult = "g" Then
GoTo JpgDisplay
Else
MsgBox "You Must Select A Document"
Close
End If
Exit Sub

Thanks

[ranman256]

if you move the db to another pc you run the risk of THAT pc not having the same libraries.
In an uncompiled db (.mdb, or accdb) , open it and get in the VBE, (ctl-G)
menu, tools, references,
it will show you the missing references. (marked MISSING)

If you do NOT have full access installed on that PC, then there's no way to determine what libraries are missing.

[RuralGuy]

Try just unchecking the MISSING library and see if it compiles.

[WAVP375]

If I started from scratch and develop the entire application on the production network, would this eliminate the problem?

[RuralGuy]

Did you try my suggestion?

[WAVP375]

Yes, same problem

[RuralGuy]

Yes, same problem

Thanks for the answer. It was worth a try.

[John_G]

If you are moving the database to an earlier version of MS Access, you need to reset the references list to use the earlier library versions that are on the production PC's.

For example, in Access 2010 you will reference Office 14 Libraries, in Access 2013 it's Office 15. One other trick I've noticed is that if you get compile errors that make no sense, e.g.. an error when referencing a function you know is a part of Access, try moving the library reference upwards in the list.

It's quite possible that you won't have to make any changes to your code, other than recompiling it.

[Micron]

You will continue to be hampered by this if some production pc's have different versions of Office and/or Access libraries installed if the IS/IT policy is to over-write the old libraries. You may need a table of references that get mapped depending on the version, or you will have to have more than one version of your base file in distribution.

[WAVP375]

Thanks guys, I think I have it sorted out.