katerina-p
asked on
Unrecognized database format Access 2007 2013
Hi All,
I have an accdb front end, which for the past 4 weeks I develop using Access 2013 on Windows 8.1 Pro. Prior to that it was developed in Access 2007 on Windows8 on a previous machine.
This gets deployed to 2 servers.
Server 1 is running Access 2013 on Windows Web Server 2008 R2
Server 2 is running Access 2007 on Windows Server 2003 SP2
Something [else] has changed in the past ~2 weeks, meaning that when attempting to open recent releases of the accdb on Server 2, the message ‘Unrecognized database format [..filename]’ appears and the accdb does not open.
• Have decompiled, compacted and repaired
• Have tried as an accde
• Same file is fine on dev machine and Server 1
• No changed to references or dlls used recently
• Some previous version accdbs which were created on the new dev machine in Access2013 can be opened OK, so not solely to do with that change
So has anyone got any suggestions as to where I need to look to fix this? Many thanks!
K.
I have an accdb front end, which for the past 4 weeks I develop using Access 2013 on Windows 8.1 Pro. Prior to that it was developed in Access 2007 on Windows8 on a previous machine.
This gets deployed to 2 servers.
Server 1 is running Access 2013 on Windows Web Server 2008 R2
Server 2 is running Access 2007 on Windows Server 2003 SP2
Something [else] has changed in the past ~2 weeks, meaning that when attempting to open recent releases of the accdb on Server 2, the message ‘Unrecognized database format [..filename]’ appears and the accdb does not open.
• Have decompiled, compacted and repaired
• Have tried as an accde
• Same file is fine on dev machine and Server 1
• No changed to references or dlls used recently
• Some previous version accdbs which were created on the new dev machine in Access2013 can be opened OK, so not solely to do with that change
So has anyone got any suggestions as to where I need to look to fix this? Many thanks!
K.
ASKER
Hi Jim,
Thanks for your response.
The deployment as follows: accdb zipped on dev machine, a copy is ftped to each station, where it's opened/used. All data is in Access backends on server 2, and some in MySQL [on Server 3...].
Thanks for your response.
As a start, anytime you mix Access versions, you always want to develop in the lowest common version, so all your develop should be done with A2007.Yep, no doubt! Far from ideal situation I know. Unfortunately don't have a copy of 2007 here anymore.
Take the file from server 1, zip it, then place it on server two. Now does it work? And are you loading the front end from the server? If so, you want to avoid this. It should be on the stations. Only thing that should be on the servers is a back end with data.
The deployment as follows: accdb zipped on dev machine, a copy is ftped to each station, where it's opened/used. All data is in Access backends on server 2, and some in MySQL [on Server 3...].
<<The deployment as follows: accdb zipped on dev machine, a copy is ftped to each station, where it's opened/used. All data is in Access backends on server 2, and some in MySQL [on Server 3...]. >>
and it's the backend that has the problem then?
Jim.
and it's the backend that has the problem then?
Jim.
ASKER
Jim,
Apologies, apologies. Server 1 (Windows 2008 and Access 2013) has backends.
K.
Apologies, apologies. Server 1 (Windows 2008 and Access 2013) has backends.
K.
ASKER
The only problem is on Server 2, older Windows and older Access. Whilst posting this I'm installing RT Access 2010 on there to see what that does (tried RT 2013 but that seemingly cannot run on Windows 2008).
ASKER
Can open the same file(s) as in OP on the older server using Runtime 2010. Not ideal though - hoping someone know exactly what causes the error in OP.
K.
K.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No real solution. Had to upgrade all round as advised.
<<So has anyone got any suggestions as to where I need to look to fix this? Many thanks!>>
As a start, anytime you mix Access versions, you always want to develop in the lowest common version, so all your develop should be done with A2007.
Second, watch out of the 32 vs 64 bit editions of Office. This is becoming more and more of a problem.
If possible, all users should be using the same edition.
Third, there are many things that might cause a problem, not just the development.
Take the file from server 1, zip it, then place it on server two. Now does it work? And are you loading the front end from the server? If so, you want to avoid this. It should be on the stations. Only thing that should be on the servers is a back end with data.
Jim.