<div>
Most likely it is caused by one or more missing references. <br>So, create a normal accdb version, and then run this on the offending machines and study the references and if any of these couldn't be resolved leading it to be marked MISSING.
</div>


<div>
Mel,<br><br>&nbsp;What you need to watch out for is 32 versus 64 bit installs. An .accde cannot be recompiled on the fly because there’s no source code as part of it. So if you compiled it on a 32 bit &nbsp;Machine then it must run on a 32 bit &nbsp;Office install. If the user has 64-bit office installed it’s not gonna fly .<br><br>Jim<br><br>
</div>


<div>
In this post :&nbsp;<a href="https://social.msdn.microsoft.com/Forums/en-US/d0daa06d-c6ac-4582-afc9-92df27ab98d3/how-to-get-programmatically-a-list-of-all-available-references-of-a-vba-project?forum=isvvba" rel="ugc nofollow">https://social.msdn.microsoft.com/Forums/en-US/d0daa06d-c6ac-4582-afc9-92df27ab98d3/how-to-get-programmatically-a-list-of-all-available-references-of-a-vba-project?forum=isvvba</a><br>there is a nice function to list all the references..just compare the lists between the "running" and the "not running" machines.
</div>


<div>
All installations are Office 32 bit. &nbsp;Our application will not even launch on an Office 64 bit installation.<br />
No missing reference appear when viewing the code using the accdb version. &nbsp;The vba/vbe dll files appear to be identical on offending machine to those on other machines. &nbsp; <br />
This issue appears to be very similar to that caused by KB3085515 update for Office 2010 about 4 years ago. &nbsp;But this is Office 2013 and that KB is not listed in the updates, nor should it be.
</div>


<div>
Shouldn't tblEmphistoryStartDate &nbsp;be tblEmphistory.StartDate ?<br>Do you have any empty procedures? &nbsp;If so, delete them all.<br>Does your VBA compile without errors?<br>Can you post the full SQL Statement of your query.
</div>


<div>
Is this a new workstation? If so, you may have a corrupt install of Office (or Windows). The Repair option sometimes doesn't do a very good job, and you have to manually uninstall and reinstall:<br><a href="https://support.office.com/en-us/article/uninstall-office-from-a-pc-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8" rel="ugc">https://support.office.com/en-us/article/uninstall-office-from-a-pc-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8</a>
</div>


<div>
Has to be references then as gustav said.<br><br>Jim.
</div>


<div>
This issue is now no longer happening on this one computer, but is also happening on another Lenova machine with the identical install of OS and Office. &nbsp;I've seen this similar error twice in my career. &nbsp;Once around 2012 when a specific brand of computer that previously had an older version of MS Access installed on it and was recently updated to Access 2007 or 2010. &nbsp;The only fix for those computers was to completely re-install the OS and then install the new version of Access. &nbsp;The other time was 4 years ago when KB3085515 update came out. &nbsp;Users started getting this error running the accde version, but using the uncompiled version of Access, the error never happened. &nbsp;In that case, uninstalling the update fixed the issue.<br />
So now I'm getting this same error again in only the accde and seemingly no resolution to the problem.
</div>


<div>
I would just add that it probably has nothing to do with the machine brand, just what is installed on it. I missed this in your question:<br><br><blockquote>If I compile the Access application on this machine, then I do not get this error when running the compiled accde version.</blockquote><br>&nbsp;That tells you right there that an existing reference was corrected when you compiled and nothing is wrong with the DB or the code. &nbsp; It's just a reference issue.<br><br>You could add some simple startup code to check the references:<br><br>Dim ref As Reference<br>If Application.BrokenReference Then<br>&nbsp; &nbsp;F<a href="https://www.engram9.info/access-2007-vba/how-microsoft-access-resolves-vba-references.html" rel="ugc"></a>or Each ref in Application.References<br>&nbsp; &nbsp; &nbsp; If ref.IsBroken then<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' Log the error<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Debug.Print ref.name &amp; " is broken."<br>&nbsp; &nbsp; &nbsp; End if<br>&nbsp; &nbsp;Next Ref<br>End If<br><br>But there is better code here:<br><br><a href="https://www.devhut.net/2017/03/03/vba-list-references/" rel="ugc">https://www.devhut.net/2017/03/03/vba-list-references/</a>&nbsp;<br><br>&nbsp;Which you might want to try out. &nbsp; It gives you a lot of detail on the references that are loaded and what is broken.<br><br>&nbsp;Also there is an old MSKB article here that gives an overview of refrences and has a few pointers in it:<br><a href="https://support.microsoft.com/en-us/help/310803/how-to-resolve-reference-issues-in-an-access-database" rel="ugc">https://support.microsoft.com/en-us/help/310803/how-to-resolve-reference-issues-in-an-access-database</a>&nbsp;<br><br>&nbsp;The one in paticular that is a gem is Refreshing the refrence list. &nbsp; Sometimes all it takes is adding a reference and then clearing it to get a DB to work. &nbsp; Not sure why or what the process is behind that, but I've often found it to be the case.<br><br>Jim.<br><br>
</div>


<div>
I added the reference code to the database and compiled it. &nbsp;When loading the compiled accde on the affected computer, no missing reference was detected.
</div>


<div>
You may need a deeper test of the references called by an AutoExec macro. <br>The attached demo shows an examples of a missing reference not marked as MISSING.<br><br>Then modify it to include the references of your application. Compile, save, and run it on the offending machine.<br><br><a href="https://filedb.experts-exchange.com/incoming/2020/03_w12/1447132/CheckReferences.accdb" rel="ugc">CheckReferences.accdb</a>
</div>


CheckReferences.accdb

<div>
If mysterious problems arise do check your references...you might reference an ocx that looks the same, &quot;feels&quot; the same but is not the same...<br />
i had a &quot;hell broke loose&quot; case &nbsp;some years ago when an Ms .ocx got &nbsp;a bit of minor upgrade...like from version 1.5.614 to version 1.5.617 (can't remember the exact .ocx, version numbers)...well everything was working great on my machine since i had the latest version and i have compiled my copy against it...guess what, &nbsp;on everyone else it crashed.... crashed really badly....when i got the ocx to same level everything started working just fine...(it might have the same size...<i>my memory is not at it's best</i>...but do check that you have the <u>exact</u> same build numbers)
</div>


<div>
Thanks to all experts who provided suggestions. &nbsp;I've learned from it and I'm sure I'll be using some of that code in the future
</div>


<div>
<div class="content wysiwyg-content">
We have an Access front end application (sql server backend) which is developed in Office 2010 and compiled using Access 2010. &nbsp;When we distribute the application, it has run with no issues on systems running Access 2010 - 2019 in retail versions, &nbsp;volume licensed editions, &nbsp;Office 365 subscriptions , on OSs from Windows 7 through Server 2016.<br />
Now we have Lenova workstation that when running simple VBA function code its giving an error. <br />
<br />
&quot;3075 function is not available in expresssions in query expression &nbsp;((tblEmphistoryStartDate) &lt;&nbsp;Date() - 1)&quot;<br />
<br />
If I compile the Access application on this machine, then I do not get this error when running the compiled accde version.<br />
The 2013 build on this computer 15.0.5111.1001. &nbsp;is the same as a server on the same network and it runs the accde compiled in 2010 without error.<br />
<br />
I'm lost as to what to look for to correct this on the workstation. &nbsp;I have run Office Repair from Control Panel and that did not correct it. &nbsp;<br />
<br />
Any suggestions are welcome.
</div>
</div>


We have an Access front end application (sql server backend) which is developed in Office 2010 and compiled using Access 2010.  When we distribute the application, it has run with no issues on systems running Access 2010 - 2019 in retail versions,  volume licensed editions,  Office 365 subscriptions , on OSs from Windows 7 through Server 2016.
Now we have Lenova workstation that when running simple VBA function code its giving an error. 

"3075 function is not available in expresssions in query expression  ((tblEmphistoryStartDate) < Date() - 1)"

If I compile the Access application on this machine, then I do not get this error when running the compiled accde version.
The 2013 build on this computer 15.0.5111.1001.  is the same as a server on the same network and it runs the accde compiled in 2010 without error.

I'm lost as to what to look for to correct this on the workstation.  I have run Office Repair from Control Panel and that did not correct it.  

Any suggestions are welcome.

Access 2013 ACCDE file not running on specific computers

Microsoft Office is an integrated suite of applications that includes Outlook, Word, Excel, Access, PowerPoint, Visio and InfoPath, along with a number of tools to assist in making the individual components work together. Coding within and between the projects is done in Visual Basic for Applications, known as VBA.

Microsoft Office

Office 365 is a group of software plus services subscriptions that provides productivity software and related services to its subscribers. Office 365 allows the use of Microsoft Office apps on Windows and OS X, provides storage space on Microsoft's cloud storage service OneDrive, and grants 60 Skype minutes per month. Office 365 includes e-mail and social networking services through hosted versions of Exchange Server, Skype for Business Server, SharePoint and Office Online, integration with Yammer, as well as access to the Office software. All of Office 365's components can be managed and configured through an online portal; users can be added manually, imported from a CSV file, or Office 365 can be set up for single sign-on with a local Active Directory using Active Directory Federation Services.

Microsoft 365

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.