Subform link problems in Access 2016

[cfljanet]

I have a main form and a subform linked together by a field call Lot Id. The Master field and Child field both reference "Lot Id". It has worked perfectly for years, until now when we upgraded to Office 2016. I now get an error "The LinkMasterFields property setting has produced this error: 'Label not defined'" when I try to enter new data in the subform.

I copied the database back onto my laptop which still has Access 2010 on it. It works perfectly.

Any suggestions? I would be grateful as I'm panicking a bit (a lot!)

[Missinglinq]

Does the error pop up with the first character you enter in a new record?

Can you edit records in the subform?

What line is hilited when the error pops?

Linq ;0)>

[cfljanet]

It pops up on entering the first character. In the sub-form I have fields "Sales Id" which is automatic, then "Lot Id" which usually auto-completes when moving to the next record, and then "Invoice". So the first character I enter is the Invoice number, and that is where the error is popping up. "Invoice" is linked to an Invoice Table by the way.

It does let me edit old data though, with no issues.

[cfljanet]

Okay, found the solution. By a process of trial and error I have found the solution. There was a command button on the form which was used for Finding Records. When the code was deleted, everything else worked fine on the form. Have no idea why this upset everything (it wasn't just the linked forms), but it seems to be working fine now. I should have tried all of this before bothering you guys, but I never thought it would be this of all things.

Thank you anyway!

[Missinglinq]

Glad you got it sussed!

Good luck with your project!

Linq ;0)>

[cfljanet]

Thank you! It's a relief to have it back to normal

I have found that 2016 has a lot of these issues, so I'm sure this is not the last of them. In case this helps anyone in the future, this one command button made all 4 command buttons on the form return the same error message (different to the one described above when entering data) - once the code was deleted on that one all the other 3 re-gained functionality. And it also solved the data entry problems that I opened this post with.

All a mystery....