By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,962 Members | 2,545 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,962 IT Pros & Developers. It's quick & easy.

Runtime Error 2424

P: 1
Greetings to the well of knowledge...

I recently upgraded from Access 2010 to Access 2016. Since then, a couple of my front ends have been throwing Run Time error 2424 (The expression you entered has a field, control, or property that Microsoft Access can't find).

I have narrowed the problem to a line of code which changes the Recordsource property (a SELECT query) of the form. The change contains the same fields; it only changes the sort of the records. I change the Recodsource property then Requery the form. Also of note: the form contains a field from the Recordsource query that is hidden. The value of this hidden field triggers whether other fields on the form are visible or not.

This procedure is executed by clicking a button on the form, at which point the run time error occurs.

What would have possibly changed in Access 2016 that would cause this behavior?

4 Weeks Ago #1
Share this Question
Share on Google+
1 Reply

Expert Mod 15k+
P: 31,492
I'm sorry to say that I don't know the answer to your question Ken.

However I would say that the Access Team in Redmond are very conscious of backwards compatibility and never introduce changes that break wxisting systems if they can help it.

Other than a compatibility issue the only thing that occurs is that something broke during the switch-over. It can sometimes be helpful to recreate an object from its constituent parts and see if the new version exhibits the same problems as the old.

Beyond that I have nothing to offer I'm afraid.

Good luck.
4 Weeks Ago #2

Post your reply

Sign in to post your reply or Sign up for a free account.