I am developing an Access application for a client. I'm using Access 2003 SP2, but the database is saved in Access 2000 format.
Said client has an existing Access application, developed under their version of Access (2002 SP3) but also in Access 2000 format. Since my app will draw some data from tables of that application, I was given a copy of that as well.
We have a bizarre problem however where we cannot open each other's files. My app runs fine on my comp and their app runs fine on theirs, but as soon as either of us tries to open the app developed on the other side, the following error pops up:
"This database is in an unexpected state; Microsoft Office Access can't open it." (Followed by a story about DAO and CompactDatabase.)
I've done some research on this error and discovered that it's often associated with corrupted databases, but I'm fairly sure that can't be the case here. It only happens when we try to open each other's databases; files that work fine when run on the end they were developed. I could see the problem being a version difference between 2002 and 2003 somehow, but thought that having the files all in Access 2000 format *should* solve that.
It gets stranger: their app is a frontend/backend one, and I only have trouble opening their backend. Their frontend - also Access 2000 format developed under 2002 SP3 - runs fine on my end too, and what's more, it has linked tables from the backend that do work correctly. I can't link to any *more* tables in the backend, but the links that are in place work correctly.
Does the above sound familiar at all? What could be causing the error I'm getting? Googling hasn't yet turned up anything for me that wasn't about either the original cause of the error message displayed (which isn't the case here) or corrupted databases (which I'm fairly sure can't be it either).
Thanks for your time!
"Any fool can defend his or her mistakes; and most fools do." -- Dale Carnegie
Said client has an existing Access application, developed under their version of Access (2002 SP3) but also in Access 2000 format. Since my app will draw some data from tables of that application, I was given a copy of that as well.
We have a bizarre problem however where we cannot open each other's files. My app runs fine on my comp and their app runs fine on theirs, but as soon as either of us tries to open the app developed on the other side, the following error pops up:
"This database is in an unexpected state; Microsoft Office Access can't open it." (Followed by a story about DAO and CompactDatabase.)
I've done some research on this error and discovered that it's often associated with corrupted databases, but I'm fairly sure that can't be the case here. It only happens when we try to open each other's databases; files that work fine when run on the end they were developed. I could see the problem being a version difference between 2002 and 2003 somehow, but thought that having the files all in Access 2000 format *should* solve that.
It gets stranger: their app is a frontend/backend one, and I only have trouble opening their backend. Their frontend - also Access 2000 format developed under 2002 SP3 - runs fine on my end too, and what's more, it has linked tables from the backend that do work correctly. I can't link to any *more* tables in the backend, but the links that are in place work correctly.
Does the above sound familiar at all? What could be causing the error I'm getting? Googling hasn't yet turned up anything for me that wasn't about either the original cause of the error message displayed (which isn't the case here) or corrupted databases (which I'm fairly sure can't be it either).
Thanks for your time!
"Any fool can defend his or her mistakes; and most fools do." -- Dale Carnegie