AnsweredAssumed Answered

Missing Re-Link possibility when changing DSN-reference of external ODBC-datasource

Question asked by TP_1 on Apr 9, 2014
Latest reply on Apr 22, 2015 by TSGal

Summary

Missing Re-Link possibility when changing DSN-reference of external ODBC-datasource

Product

FileMaker Pro

Version

13.0v2          [probably any]

Operating system version

Windows 7 Enterprise SP1 (x64)          [probably any]

Description of the issue

When changing the DSN-reference of an external ODBC-datasource to a new DSN which references a new database, but the old database still exists, the Re-Link button is not shown. So after changing, the new database should be accessed, but still the old database is accessed, even though you chose the new DSN refering to the new database.


(A similar problem is when you want to change the base-folder of an externally stored container, but the old folder still contains data. FileMaker wouldn't let you change the base-folder in this case. The workaround is simimal to the one from the ODBC problem above. See below.)

Steps to reproduce the problem

Use MySQL v5.6 compatible for the external databases (old/new) and MySQL Connector/ODBC v5.2.6 (32-bit) to create the System-DSNs for both databases.

Expected result

See above.

Actual result

See above.

Exact text of any error message(s) that appear

-

Configuration information

[BTW: Why is there no possibility to create an external table (for example coming from an ODBC-datasource) in your FileMaker-project, without creating a table-reference in your FileMaker-reference-graph first?]

Workaround

Change the old database's name, re-open your FileMaker-project, click the now shown Re-Link button after DSN had been changed, change the old database's name back.


(To change the base-folder of an externally stored container, when the old base-folder is not empty: Rename the old base-folder, change the base-folder-setting to the new one, rename the old base-folder.)

Outcomes