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.
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.