Access 2007 and 2010

[neilhwilliams]

Hi,

I brought away a client's access 2007 db and made changes to it. I only have access 2010, so I made the chages within there.

When I took the db back to the client, it came up with a message that the file either wasn't a db or it was corrupt.

Does this sound like a backward compatibility issue ? Bit severe not to open it up at all or even recognise the fact it is an .accdb when all is said and done.

I need to know if it is a compatibilty error message before I go spending time fixing the compatibility issues if really there's something completely different going on here.

Thanks

 

[DJkarl]

Unless you did a SaveAs and chose the 2007 format it likely would not be readable by the older Access version. This is not a backwards compatability issue but more a forwards compatability issue, you have the newer version and you could read the old format just fine, if you made changes and saved it in the newest format, the old database would have no idea how to read it in.

 

[neilhwilliams]

Hmmm. Thanks for that... however... I have made changes to this before in the same manner without the same issue... So not sure that's the problem.....and the save dialog doesn't allow me to save it as anything but 'Microsoft Access database'... it doesn't offer alternatives such as 2.0 or 2007.

I just wonder if perhaps it's more to do with the fact this time I changed a password for the Db (as asked to) and the encryption 'stuff' in 2010 is not back compatible.

Would it still have the effect of blowing up without even acknowledging it's an .accdb extension though ? Surely it would try... and then give me a more meaningful error than 'This is not a db or it's corrupt' ?

 

[GinaWhipp]

You hit the nail on the head... as a rule, *any* changes I make in a database I use the earliest version possible to make changes. Unfortunmately, it gives no *real* message... It is a problem because they both have the same extension so the message, itself, makes no sense, unless you know what happened, in which case, you do.

I would recommend TeamViewer to get into their system and make the changes that way.

 

[neilhwilliams]

Thanks Ginawhipp. I wonder if I take the encryption off again it will be ok, or is the damage done?

 

[GinaWhipp]

Here's what I would do... save in an earlier version, like 2003, provided you used no elements new to 2007, then repoen in Access 3007 and convert to it. And *never* do that again...

PLEASE make a back up first!!!

 

[neilhwilliams]

It was a bit naive, but I got away with it once. I like the assumption that I have access to multi versions of accessdb !

It was only a one off so not worth the investment. If my fix doesn't work, I'll just sit in the client's office and do the work. It's only half a mile away and the development curve is done so should take a fraction of the time.

 

[CBrighton]

I have 3 PC's on my desk specifically because I need access to Access 97, Access 2003 & Access 2007 and don't want to keep swapping which version I am running on a single PC as this tends to cause reference issues, etc.

 

[GinaWhipp]

I have *finally* gotten down to two because I have no Clients left on Access 97. The other have multiple versions of Access or I would three machines as I go up to Access 2010. (The fourth one sits in the attic hoping no one ever asks again for a fix to an Access 97 database.)