[AccessD] What problems converting A2K3 mdb to A2K7?

If the database uses any code with references set check that these are still
set. I was asked to fix a database that was moved to Access 2007 and most of
the problems were with broken references.  The biggest PITA was figuring out
where the menu items are in 2007.

Doug 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tina Norris
Fields
Sent: Wednesday, August 29, 2007 10:44 AM
To: DatabaseAdvisors-Access
Subject: [AccessD] What problems converting A2K3 mdb to A2K7?

Hi All,

A client called with this story:  We had a functioning database developed in
A2K3.  We gave the data to an off-site developer who did some redesign work.
While the database was away being reworked, we upgraded in the office to
A2K7.  The database now seems to be missing some fields and is not really
functional.

My first impression (I have not looked at the database yet) is that the
difficulties probably are associated with the off-site rework rather than
the upgrade.  But, I thought I'd check out what to watch out for when I do
go look at the database.

Thanks for any advice and information on A2K3-A2K7 issues.

Tina
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com