Ummm, the message is generic for forms and reports. It could be either.
Somewhere, something is being called and it can't resolve it. The message refers to 2017-2018-2019 but the table isn't named that.
I'd start with looking at the db properties to see if an opening form is being called automatically based on your comments.
And no, I wouldn't start over as opposed to finding the problem. If it is a default opening form or Autoexec macro and you don't know what I mean, you'll rebuild everything in the db and still have the problem. It seems to work for now as you say - but it may be because you haven't tried to use whatever looks at the broken reference (if it's not an opening form/macro issue).
By any chance you are missing a table that was maybe linked in the db you copied from?
Last edited by Micron; 10-21-2018 at 10:29 PM.
Reason: added info
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.