Forum Discussion
This Object was saved in an invalid format and cannot be read
George_Hepworth Thank you so much for the reply! I've now tried to decompile and recompile, unfortunately that has not solved the issue, I'll try this save as a text file method. 
I'm really not that experienced at access but I find it very curious that this error only happens on my main computer, when I launch the database on the data entry computer it prints the report just fine, Also I tried editing the reports on another 3rd computer and it worked until recently (now it throws the same error).
Would you know if splitting the database will prevent this error?
Again thank you so much for your time! I really appreciate the help , I'll keep the forum updated!
Splitting the accdb probably wouldn't make that much difference but it's always a good idea to split every relational database application in any event.
The difference between behavior on different computers may be related to different version of Office. Is everyone working with the same version?
It looks like everyone is on Access 2016, would there be different software versions (like v1.01 or something of that sort?).
Hm. I just re-read your initial post. I forgot you had not yet split the accdb into the Interface components in a Front End and the data in tables in a Back End.
Do that now. Do it with a known good copy of the accdb. Put the BE in a shared location. Give every user their own copy of the known good FE. Keep a master copy of the known good FE away from any other user so you can recover from it if necessary. Never let two users open the same copy of an FE.
And make sure your data is backed up regularly (daily or more often would be better.)If everyone is on the same version of Office, and you are all receiving updates via the same channel, you shouldn't have a problem in that regard. There can be slight differences if some computers are on, say a monthly update and others on a longer schedule. I was more concerned here with versions like 2007 and 2016 or something. That's when issues like this could happen.
Given that some people's computers do not experience the problem while others do, I'd probably go ahead and give everyone a new copy of the accdb FE, one which you can confirm doesn't have this problem and go from there.
Depending on your IT policies, it would also be a good idea to repair the Office installations on all computers as well.
Otherwise, the fact that there is a discrepancy is actually a good sign in one way. It suggests that the master copy of the accdb FE from which each user's copy was made is okay.