How to upgrade from MS-Access 97 to MS-Access 2010?

The same observations apply here as to those for converting Access97 to2003 databases. DMW hear of major problems in converting modules.

 

You may experience database problems if you install both Access97 and Office2007 or Office2010 on the same PC. There can be interference not only between the versions of Access but also between Access97 and other programs in Microsoft Office.

 

DMW no longer attempts to mix Access97 with programs from later versions of Office. Instead an old PC is kept solely for the purpose of running Access97.

 There is a 'convert database' feature in Access2003. In DMW's experience, this rarely makes the conversion without some errors.

 

If your database is in the form of an MDE file, there are utilities advertised that claim to unlock MDEs. Once unlocked, so the claim goes, you can make changes to your MDE.

 

DMW have tried one unlocker program that gets mentioned a lot on the Web. In those of Access97 MDEs that DMW have 'unlocked' using it, the majority of forms and reports will not go into design view. Furthermore, none of the VBA modules are accessible.

 

So now may be the best time to review the functionality of your database prior to offering to tender for the rewrite

I never used MS Access in my work, but I have tried to find a suitable answers for your case:
1- There have been a lot of changes between Access 97 and 2010.
Each upgrade (97 to 2003, 2003 to 2007, etc.) had quirks that you needed to be aware of.
The conversions weren't usually simple tasks, especially when you had a complicated database with lots of things going on.
Taking the leap from 97 directly to 2010 will be almost impossible in your situation.
However, it can be done if you take it slow and address the problems at each stage.
The issue is that it might take more time than you are willing to give to it.
In my search for answers for you, I came across companies that did this type of conversion for you.
This, to me, is one more indication that this isn't something you just let a wizard do (otherwise, who would pay for the service).
Here is one of the companies I found: http://www.consultdmw.com/convert-access-97-database.htm I've never used them so I'm not endorsing them.
I'm just using them as an example.
There are also resources out there of people that have walked down this path and shared their experience.
These might be valuable to you in determining if you want to go down this path and if so, what to look out for.
Here is an example: http://chentiangemalc.wordpress.com/2011/03/24/upgrading-access-97-application-to-access-2010/
2- Try upgrading incrementally, i.e.
Access 97 to Access 2003 to Access 2007 to access 2010.
Going from Access 97 to 2010 may be too big of a leap.
An Access 2007 application should be runnable without modification in Access 2010
3- Converting an Existing Access Application to Access 2003 If you are considering upgrading from Access 97 or 2000 to Access 2007 or 2010, it's recommended that you first convert the project to be compatible with Access 2003.
For information on how to convert an Access application to be Access 2003 compatible, see the following site: http://office.microsoft.com/en-us/access/HP051863781033.aspx.
It's possible that converting your Access application to be compatible with Access 2003 will occur quite smoothly.
For information on possible conversion problems or usability issues to be avoided in Access 2003, see the following site: http://www.allenbrowne.com/ser-48.html.
As is suggested on this site, it's important that your copy of Access 2003 has the latest updates to help eliminate some possible problems.
Once you have your project saved in a format compatible with Access 2003, you can then save the file as a Access 2007 file.
Some of the potential pitfalls of this conversion are covered in the next section.
When upgrading some Access applications, it may be possible to skip the conversion to Access 2003 and go straight to an Access 2007 file.
However if you have any problems doing so, it would be best to first convert your application to Access 2003 and then to Access 2007.
Incase you are considering converting your Access application to Access 2003 and selling it with the Access 2003 Runtime, you will need to purchase the rights to distribute the Runtime.
See the following site for details: http://office.microsoft.com/en-us/access/ha011208861033.aspx.
Depending on the features used in your application, it may be possible to distribute your application with the Access 2007 Runtime which can be freely distributed: http://www.microsoft.com/downloads/details.aspx?familyid=d9ae78d9-9dc6-4b38-9fa6-2c745a175aed&displaylang=en more data on website: http://www.sagekey.com/support_forum.aspx?g=posts&t=393 I hope that will be useful and helpful to your situation, and try to read it carefully before you beginning in use and start confusing best wishes

With MS-Access 2010, you can import objects into a new empty MDB from an earlier version database in stages.
First import tables, and verify data imported correctly.
Next import standard and class modules.
Run Debug->Compile, and fix any errors the compiler complains about.
Might have to add references as needed.
Then import the forms and run Debug->Compile again.
Same for reports, if any.
Best case, you would have few fixes needed to get it running with 2010.
If the amount of fixup work is unreasonable, then consider farming it out to a service.
But I suggest you at least try the manual import method first.
You shouldn't have to invest too much time to see whether it's worthwhile to continue.

Quick Answers: - backing up of your old Ms-Access database may be a good idea.
- yes, you are to create new database in Access 2010 then import then old database.
- It should performed even better, if the conversion are done correctly.
- yes, a lot of issues, example finding where buttons in the new tabs are but you can handle that soon..
For the main procedure i found it a bit hard to type all in here, but please find this page: http://chentiangemalc.wordpress.com/2011/03/24/upgrading-access-97-application-to-access-2010/ a very helpful concept how to handle all the conversion process.
I hope it helps, if not please let us know then I've to prepare the tutorial myself.

Below are some reviews about this issue: Compare: http://www.opengatesw.net/ms-access-tutorials/Microsoft-Access-Version-Comparison.htm http://www.amazon.com/Microsoft-077-05753-Access-2010/product-reviews/B0039L2XD4 http://www.pcmag.com/article2/0,2817,2366672,00.asp

Open Microsoft Access 2010 On the File menu, click Open.
Select the database you'd like to convert and open it.
On the File menu, click Save & Publish.
Select Access Database from the section entitled "Database File Types".
Click the Save As button.
Provide a file name when prompted and click Save.

There have been a lot of changes between Access 97 and 2010.
Each upgrade (97 to 2003, 2003 to 2007, etc.) had quirks that you needed to be aware of.
The conversions weren't usually simple tasks, especially when you had a complicated database with lots of things going on.
Taking the leap from 97 directly to 2010 will be almost impossible in your situation.
However, it can be done if you take it slow and address the problems at each stage.
The issue is that it might take more time than you are willing to give to it.
In my search for answers for you, I came across companies that did this type of conversion for you.
This, to me, is one more indication that this isn't something you just let a wizard do (otherwise, who would pay for the service).
Here is one of the companies I found: http://www.consultdmw.com/convert-access-97-database.htm I've never used them so I'm not endorsing them.
I'm just using them as an example.
There are also resources out there of people that have walked down this path and shared their experience.
These might be valuable to you in determining if you want to go down this path and if so, what to look out for.
Here is an example: http://chentiangemalc.wordpress.com/2011/03/24/upgrading-access-97-application-to-access-2010/

I would suggest having this done by a service provider, also make sure you back up your databases