Memo reappears 11 years later

[DBinPhilly]

A customer has a package that has been running under MS Access 2000 for a long time (11 years). Yesterday he replaced his computer and I installed MS Access 2010 runtime and moved the database to the new computer.

Today he was keying into the reporting system and a memo field that was in a record from November, 2000 (the 115th record in the database) appeared in the same field as he was keying the 1878th record in the database.

Any opinions gratefully accepted!

[HiTechCoach]

I have been helping others convert their 2000 databases. I did not create them. When taking an Access 2000 database and running it with Access 2003 I have to do some tweaking. When running with Access 2007 there is a lot of tweaking I have to do. Still waiting on Office 2010 SP1 to start using Access 2010 in production.

Until Office 2010 SP1 is released I would not use Access 2010. And only then after you have done lots of testing I would use the Access 2007 runtime with the SP2 update.


Going from Access 2000 to any newer version you need to do lots of testing.

[DBinPhilly]

Ouch! that is not good news.

I will look into falling back to Access 2007 Runtime in this instance.

But: I am going live with another instance of Access 2010 very shortly. This is a conversion from a MS Access 2003 Project (.adp). So you believe I should anticipate trouble?

[HiTechCoach]

ADP's have been depreciation starting with 2007. I am not sure how well Acess 2010 supports ADPs. I would do lots of testing.


Good news in that Office 2010 SP1 update should be out any day now..