By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,121 Members | 1,723 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,121 IT Pros & Developers. It's quick & easy.

Moving to Access 2007

P: n/a
I have an old database which started out life in the Access 2 days!
It's full of lots of stuff which I'm not convinced is relevant any
longer. Would a good way forward be to create a new, blank database in
Access 2007 and then import the existing objects, re-create the
relationships etc? That way I can just bring in the stuff that's
currently in use and, hopefully, have a better chance of avoiding
database corruption. The alternative, I suppose, is to convert the
whole database and then delete the unwanted objects but the former
seems a cleaner approach
Dec 20 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Yes: importing the A2 stuff into a new (blank) database could be a good
idea.

It gives you much finer control over what's going on. If there are problems
(e.g. a corrupt form), importing the other stuff is probably the only way to
do it.

Unless you have reason to suspect problems with the relationships or
duplicated indexes, you can import those. Access does that by default. (You
do have to redesign the Relationships Window layout, of course.)

Some of the code could need updating. If you have gone to other versions
after 2, it may be using the Compatibility Layer. This kind of thing is not
difficult to replace. If it has only ever been in Access 2, you may need to
update some 16-bit things (e.g. API calls.)

You may find that the Seed of the AutoNumbers has gone haywire after
importing. If so, this code will loop through the tables and fix it for you:
http://allenbrowne.com/ser-40.html

Other suggestions on updating from Access 1/2:
http://allenbrowne.com/gotcha27.html
or from Access 97:
http://allenbrowne.com/ser-48.html
and info about the changes to adjust to in Access 2007:
http://allenbrowne.com/Access2007.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"anthony" <an*************@gmail.comwrote in message
news:3a**********************************@y5g2000h sf.googlegroups.com...
>I have an old database which started out life in the Access 2 days!
It's full of lots of stuff which I'm not convinced is relevant any
longer. Would a good way forward be to create a new, blank database in
Access 2007 and then import the existing objects, re-create the
relationships etc? That way I can just bring in the stuff that's
currently in use and, hopefully, have a better chance of avoiding
database corruption. The alternative, I suppose, is to convert the
whole database and then delete the unwanted objects but the former
seems a cleaner approach
Dec 20 '07 #2

P: n/a
Many thanks, as always
Dec 20 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.