Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Going from Version 2000 to 2013 back to 2000.

Status
Not open for further replies.

Goofus828

Programmer
Nov 9, 2005
127
US
Hi all,
At work we have a critical Billing application (Access 2000) that stopped working in Access 2000.
And by stop working I mean ODBC errors where popping up when opening the database.

It might have been to mangled ODBC connections that were trying to connect to 3 VFP tables.
We repaired the connections, but were still unable to get past the ODBC Errors.

I then used Access 2013 to load the 2000 version and save it as a 2013 version.
That version opened fine with no ODBC error messages.
I then save the 2013 version back to the 2000 version.
I opened that in 2013 and again no errors

I do not have 2000 to testing.

The person who usually run this is concerned that going from 2000->2013->2000 will affect the database.

I did not change one thing in the tables or forms or queries.

Is there a reason for concern?

Any insight would be grateful.
 
As long as nothing was modified when it was a 2013 DB, you probably should be okay (provided the scale back to 2000 works correctly). Did you try (in Access 2000) to create a new database and import all the objects. Sometimes that will 'correct' odd errors.
 
Thanks Kray!
I will pass that on and see if it works.
[smile]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top