Answered by:
relink MySQL then Access

Question
-
Access 2013 .accdb
The front end in production is linking to MySQL tables.
I have a replica of the tables in an Access back end file.
Re-linking a copy of the front end from MySQL to Access using the Linked Table Manager takes me thru the Select/Create New Data Source pop up screens - because I am supposing it is expecting to relink via ODBC to MySQL.
But though I believe I step through it all correctly - it goes into never-never land and does not result in a new path. The 'REFRESHING LINKED TABLES' comment remains in the lower right frame. I limited this down to a single table. It doesn't actually freeze in that the cursor is fine and I can check the Cancel button in the Create New Data Source pop up - and bail out. It just never completes any relink.
I can of course delete those linked table, and set up new links to Access - though it is more work.
Just thought I would sanity check this with others that may have wrestled with this same environment.
Friday, January 20, 2017 6:08 PM
Answers
-
I appreciate the input. No definitely I have not tried this approach.
In my case/post the primary reason of raising visibility of this issue is in regard to the feature set of the product; which is to say - using Link Table Manager doesn't seem to work IF the prior links are ODBC and the new links are .accdb
I was basically wondering if this is a bug or if indeed it isn't suppose to be able to relink a different file type and one is expected to re-link in a different fashion (such as your suggestion, or by deleting tables and setting up new links).
I can accept that the definition of "relinking" (via Link Table Manager) is like-for-like and so it not working in a switch between link types is perhaps standard operating procedure. Just wanted to sanity check this for my own clarification.
If I now understand correctly that you are changing from one database type to another, then I would highly recommend deleting the current links and adding new links to the native tables. Most relinking is performed to insure that any schema changes to the underlying tables are updated, or when a database location has changed. I wouldn't recommend it for changing from a database server table, such as SQL Server, MySQL, Oracle, etc., to a native Access database table.Paul ~~~~ Microsoft MVP (Visual Basic)
- Marked as answer by msdnPublicIdentity Monday, January 23, 2017 2:03 PM
Friday, January 20, 2017 10:56 PM
All replies
-
Have you tried re-linking through code? It might give you some idea of what the problem is.
https://blogs.office.com/2012/08/03/automatically-relink-microsoft-access-tables/
Paul ~~~~ Microsoft MVP (Visual Basic)
Friday, January 20, 2017 8:30 PM -
I appreciate the input. No definitely I have not tried this approach.
In my case/post the primary reason of raising visibility of this issue is in regard to the feature set of the product; which is to say - using Link Table Manager doesn't seem to work IF the prior links are ODBC and the new links are .accdb
I was basically wondering if this is a bug or if indeed it isn't suppose to be able to relink a different file type and one is expected to re-link in a different fashion (such as your suggestion, or by deleting tables and setting up new links).
I can accept that the definition of "relinking" (via Link Table Manager) is like-for-like and so it not working in a switch between link types is perhaps standard operating procedure. Just wanted to sanity check this for my own clarification.
Friday, January 20, 2017 9:32 PM -
I appreciate the input. No definitely I have not tried this approach.
In my case/post the primary reason of raising visibility of this issue is in regard to the feature set of the product; which is to say - using Link Table Manager doesn't seem to work IF the prior links are ODBC and the new links are .accdb
I was basically wondering if this is a bug or if indeed it isn't suppose to be able to relink a different file type and one is expected to re-link in a different fashion (such as your suggestion, or by deleting tables and setting up new links).
I can accept that the definition of "relinking" (via Link Table Manager) is like-for-like and so it not working in a switch between link types is perhaps standard operating procedure. Just wanted to sanity check this for my own clarification.
If I now understand correctly that you are changing from one database type to another, then I would highly recommend deleting the current links and adding new links to the native tables. Most relinking is performed to insure that any schema changes to the underlying tables are updated, or when a database location has changed. I wouldn't recommend it for changing from a database server table, such as SQL Server, MySQL, Oracle, etc., to a native Access database table.Paul ~~~~ Microsoft MVP (Visual Basic)
- Marked as answer by msdnPublicIdentity Monday, January 23, 2017 2:03 PM
Friday, January 20, 2017 10:56 PM -
thanks that is exactly the sanity check I was seeking
Monday, January 23, 2017 2:03 PM