Link to home
Start Free TrialLog in
Avatar of morinia
moriniaFlag for United States of America

asked on

Converting Access 2000 Database to Access 2003

Experts,

I need to convert an Access 2000 Database to Access 2003.  Does anyone know the best way to do this?
SOLUTION
Avatar of gdarcan
gdarcan

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Scott McDaniel (EE MVE )
As I wrote in your other question, the default format for 2003 was Access 2000, so in most cases no conversion is needed.
I'm surprised that you would choose to go to 2003, since that application is over 10 years old and there are three newer (4 if you count Office 365) versions.  Your 2000 data is still accessible in the .mdb format, even with an Office 2007/2010 front end.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of morinia

ASKER

Experts,

I have noticed a proclvity on my machine.  I see Access 2003 and Access 2010 installed on my machine.  However, when I create a new Access Database it is Access 2000.

As stated earlier I am runnng on Windows 7.  

Why would a new access Database be Access 2000?
[3rd times the charm, perhaps]

The default format for 2003 was Access 2000. If you create a .mdb file using 2007/2010, the format for THAT is 2000. I don't think you can save a .mdb file created in 2007/2010 in a format other than 2000, but I've never tried to do it.
Avatar of morinia

ASKER

Scott,

I have some databases that say Access 2000 and others that say Access 2003.  There is an option to convert from Access 2000 to Access 2003 -2007.

But thanks for explaining why my new databases are Access 2000.  When I read that Access 2000 is not compatible with Windows 7, do you know what that means?

Is is the Access database or the Access Application.  I am running Windows 7.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of morinia

ASKER

Scott,

Thanks for you patience.  There are no validation rules in the database.  That was one of the first things I searched for.

In essence, every program is using the same logic to create an update statement and then update.

It is only this database/program that has the error.  When the same SQL statement is executed in a newly created database, it works fine.  This is both inside of a macro and through SQL.

This is why when I noticed it was Access 2000, I thought that was the issue.  However, I noticed most all of the Databases are Access 2000 except for one.  

I am going to have someone else run the application from their PC to see if there is an issue unrelated to Windows 7 and my pc configuration or there is another problem and it just happend to surface when I started running the job.

I want to rule out all scenarios.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of morinia

ASKER

There may have been some corruption when the database was restored.  However, through all of your responses I have learned about the different versions of Microsoft Access.  

There will be a conversion process of upgrading these programs to Access 2010 which is currently available on our site.