For about 12 years, we've had a FileMaker database import external data from a .mdb (Access) database that has data that is downloaded from some equipment. The process has survived several computer upgrades (Windows XP and Windows 7) and FileMaker version upgrades (created in 7 and currently running in 16). It broke when we moved into the Windows 10 environment. The script is set up to retrieve the data from the .mdb file and it says it can't access the file. So when I dive into the script and try to specify the ODBC connection it now asks for a username and password. We've never had a user name or password tied to either the .mdb file, the ODBC connection, or the FileMaker file. But no matter what we try, we can't get past this step. Is this a bug? What am I missing here?
Thanks in advance.
On windows 7 (VMware on OSX), using FMP17 and Microsoft Access 2016
Trying to do a ODBC import and selecting the datasource, I get asked for Username and password, even if the Access DB is not password protected.
The data sources are correct (tested from Livecode) and should be working without user name and password.
On the properties of the ODBC pane setup the path seems correct (not pointing to 32): %windir%\SysWOW64\odbcad32.exe
What am I missing?
Does anyone have experience and/or success using a 4D database as an external datasource through ODBC. I can add the system DSN and add it to FMP. Once I attempt to view the tables in the 4D database, I receive an error that the "ODBC connection is not compatible". Does anyone have a work around or suggestions? Thanks!
By Christopher Gauntt
I installed FileMaker Pro ODBC drivers, and was able to access the data with queries from Microsoft Excel.
However, when I tried to access the same data with the same driver using Microsoft Visual Studio 2015, it could see the table occurrences, but it couldn't find any of the data columns. It came back with the following error:
" Error at Data Flow Task [ODBC Source ]: There was an error while trying to get schema information. Table has no columns."
I got the same error, no matter which table occurrence I selected.
Has anyone else run into this and solved it?
I have been google searching without much luck. Although I found one post of someone who claimed they were able to do it with Microsoft Visual Studio 2017, so maybe an upgrade is in order?
Thanks in advance,
In several tables of our solution there are records being created that have something like, "com.prosc.jdbc.JDBCUtils test d81e5f35-4f7c-4c53-92c1-bc32e3700094" in every field. Today I found 3 tables with collectively 150 records like this... this has been happening on an irregular basis since mirrorsync was implemented several months ago. Is this coincidence or something someone has seen before?