Upgrading 2002 Databases to MS 2007

[khwaja]

I have some very well established DBs which are being used by a large number of users. Due to an impending upgrade to Office 2007, I have been asked to upgrade my systems as well. First question is can I continue using 2002 version dbs in Office 2007 environment? If not, and I might just upgrade to take advantage of better feaures in 2007, then what are the implications and how to deal with issues I might come across. If someone has had a similar experience, would love to have their feedback.

 

[Alansidman]

You can continue to use 2002 Access Databases in Access 2007. I do this and have no issues.
Alan

 

[Galaxiom]

Access 2007 was mostly a cosmetic change to the interface to match the new Office Suite. The change to database format itself was still a work in progress that was not completed unil 2010.

The file format itself does have some new features but that doesn't mean having to use them. Most experienced developers will advise you NOT to use Multivalue fields. I strongly advise you NOT to use Split Forms. They really are only a beginner's tool that runs out of functionality as you try to develop them further with VBA.

It may also be important to know that database files in 2007 format (accdb, accde etc) cannot be digitally signed. Only a complete package can be signed and this is much clumsier than simply signing the file for distribution. This feature was restored in the A2010 accd* format. 2010 files are not necessarily backwards compatible with 2007.

If upgrading it is better to bypass 2007 and go straight to 2010. Stick with mdb and mde files if you are developing in A2007.

 

[khwaja]

Thanks a lot for your insights. I am inclined to keep DBs in their existing format but my only concern is (after opening a few DBs at home where I have Windows 7 and MS Office 2007) there may be a lot of errors with a such a large application as mine. I don't exactly remember errors which were generated when I opened a couple of personal applications but I can take note of those and share with you.

 

[gemma-the-husky]

i have a complex A2003 app (mde). when trying to run this in A2007 I get tiny errors here and there - some forms won't open.

So i end up rebuilding the app to have a A2003 version, and an A2007 version.

I get the feeling that there are odd, tiny things here and there that may not work 100%. with a critical enterprise wide app, all i can say is i would try and test very carefully before committing.

I think if you are issuing mdb's rather tha mde#s then you are less likely to have problems.

 

[shadow9449]

One important point to keep in mind is that you will no longer be able to edit your toolbars and menu bars if you are using an Access XP database with Access 2007. That is an important consideration if you intend to keep the databases in Access XP format and continue developing.

SHADOW

 

[Galaxiom]

i have a complex A2003 app (mde). when trying to run this in A2007 I get tiny errors here and there - some forms won't open.

Do you have any clues to what it is about those forms that stops them working?

I get the feeling that there are odd, tiny things here and there that may not work 100%.

What kinds of things?

I think if you are issuing mdb's rather tha mde#s then you are less likely to have problems.

Any suggestion why would that be the case? The mde should be running exactly the same code as the mdb.