[ODBC-332] Old DSN cannot be find to import when old ODBC version is uninstalled and new version installed in Excel Created: 2021-08-03 Updated: 2021-08-03 Resolved: 2021-08-03 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Anel Husakovic | Assignee: | Lawrin Novitsky |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Description |
|
I'm not sure is this related to ODBC or Excel, but let me report. I have first created DSN with "ODBC Data Source (32/64 bit) " and installed from https://downloads.mariadb.org/connector-odbc/ MariaDB ODBC 3.13. And reason for that is that is using 32 bit version. However, when I tried to look for DSN there are 2 ways (
1. Data Connection Wizard Additionally, we cannot add new DSN if old DSN exists (no MariaDB ODBC option to use). |
| Comments |
| Comment by Lawrin Novitsky [ 2021-08-03 ] |
|
I don't think there is anything wrong here. There 32 and 64b drivers. There are ODBC DS administrator for 32b and 64b. If drivers have been installed for both architectures, DSN may exist for both. Excel usually is 32b application, and thus looks for 32b Drivers/DSN's. Thus 64b driver/dsn is not visible. Or vice versa. |
| Comment by Anel Husakovic [ 2021-08-03 ] |
|
Lawrin ok, how to specify , when building from source, 32b MariaDB ODBC driver to be built? |
| Comment by Anel Husakovic [ 2021-08-03 ] |
|
Found use -A Win32 with cmake. |