Going back to version 2007?

[deguza]

Hello all:



I discovered that I have version 14 of Access, and colleagues have 12. (I guess mine is referred to as 2007 and theirs is 2003.) When I did some maintenance on the database, Access apparently wrote it as version 14, and now colleagues cannot access it on our shared network folder.

I tried the "Save as" option to see if I can write as an earlier version, it won't come up with an option to write it as version 12.

I am looking into upgrading the colleagues Access but this is controlled by the IT department and I am not sure if they will be able to do it in a timely manner. (They may not be able to do it at all, because of all sorts of reasons, real or imaginary...)

Any advice so that I do not have to go back to an archival copy?

Thanks

[rivereridanus]

If you didn't make any 2007-specific code or macro changes, try making a copy of the db while it's closed and renaming the file extension back from .accdb to .mdb. I would only try this on a copy so that you don't lose your data or corrupt the only copy you have- but it's worth a shot.

[June7]

Actually, 14 is Access 2010 and 12 is Access 2007. If the original file extension was mdb then it was an Access 2003 (or earlier) file.

It has been my experience that if a accdb does not have 2010 specific features, 2007 will often open, but not always. Review http://answers.microsoft.com/en-us/o...9-509349c665c4

Is this a split design?

[deguza]

It is not a split design. I believe the original also had .accdb.

The only change I made was to put a password, and in the process Access encrypted the DB.

If you didn't make any 2007-specific code or macro changes, try making a copy of the db while it's closed and renaming the file extension back from .accdb to .mdb. I would only try this on a copy so that you don't lose your data or corrupt the only copy you have- but it's worth a shot.

If it matters, another poster pointed out that I actually have 2010, and the rest 2007.

[ItsMe]

Another thing to consider is that when you open a file, MDB or ACDDB, etc., the version of Access you use to open said file will have an effect on the file. Access 2007 will do a Just In Time compilation of the file. Access 2010 will do a Just In Time compilation of the file, Access 2003 will.....

To avoid conflicts, I do not allow random access to files. Provide each user their own copy of a front end file they store locally on their machine. Have the FE file link to a back end file on the share.

If you develop front end files using Access 2010, make sure you do not include features and or code that is not backward compatible (mentioned in previous posts).

If you create accde files, make sure Users use the same version or later to run the app.

[deguza]

I am in the process of implementing a process and will take your suggestion into consideration. Thank you.

Another thing to consider is that when you open a file, MDB or ACDDB, etc., the version of Access you use to open said file will have an effect on the file. Access 2007 will do a Just In Time compilation of the file. Access 2010 will do a Just In Time compilation of the file, Access 2003 will.....

To avoid conflicts, I do not allow random access to files. Provide each user their own copy of a front end file they store locally on their machine. Have the FE file link to a back end file on the share.

If you develop front end files using Access 2010, make sure you do not include features and or code that is not backward compatible (mentioned in previous posts).

If you create accde files, make sure Users use the same version or later to run the app.