[AccessD] What problems converting A2K3 mdb to A2K7?

Tina,

I have converted my Social Service management from 2003 to 07.
It is about 35 meg. I had no issues at all. Just do not try
running the MDB under 2007. I ran into all kinds of corruption
of the database when I did that. But after converting it to
the 07 format, everything was smooth sailing with it.

So, I would say it is 99% probable that it is the rework.

Robert

At 10:25 AM 8/30/2007, you wrote:
>Date: Wed, 29 Aug 2007 13:44:05 -0400
>From: Tina Norris Fields <tinanfields at torchlake.com>
>Subject: [AccessD] What problems converting A2K3 mdb to A2K7?
>To: DatabaseAdvisors-Access <accessd at databaseadvisors.com>
>Message-ID: <46D5B065.7020200 at torchlake.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>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