Error: This Object was saved in an invlid format and cannot be read.

[AccessBeetle]

There is an application created in Access 2003 and VBA. It is used by 18 different locations. 17 of them are running perfectly fine but one location has following problem:
There is report called "Annual Report". If someone tries to open this report from switchboard, it says "This object was saved in an invalid format and cannot be read".
I tried to export the fresh copy of that report from my backup copy. It runs fine for first time use, meaning, if someone opens that report for the first time and enters some data, it runs fine. When they close the application and try to open it again it will again gives the same error as mentioned above.
Please help. Is this a corrupltion issue? How to solve it if it is one?

[missinglinq]

Is this app split into a front end/back end configuration, as all multi-user apps should be?

Linq ;0)>

[AccessBeetle]

Unfortunately not.
Now we are thinking of doing that but before that I have to fix this error.

[missinglinq]

Multiple-users on an unsplit Access database can cause all kinds of problems including, but not limited to, corruption, timing woes and the very type of behavior you're experiencing. You need to split the database!

Linq ;0)>

[AccessBeetle]

If I split the database, how should I deploy it to the users in the field. I mean do I need to copy both FE and BE files to there PCs or just FE? (I guess it is a dumb question but I wanted to make sure i am on a right path)
Also, if I split it would it solve the error I am having??
Thanks for the help missinglinq

[Scott A]

You just need to implement the front end (FE). On the network, you just need the backend there and the user's FE will connect to it. And splitting the database will not always solve this problem, but if the user's front-end is corrupt (which still happens depending on the user's machine), you will just need to copy over a good version to their drive. Sometimes connectivity problems...or hiccups as I refer to them...between the front-end (on the local drive) and back-end (on the network) will produce this error too.