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?
I have a solution that has been working well for several months and suddenly broke. This may have been perpetuated by the last round of windows security updates. I have a list of orders displayed in a portal. The source of the portal is SQL Native 11 ODBC data. Consisting of a header table and several related tables. Clicking on a portal row will create a new Filemaker record and populate it with the related ODBC data. This will work for several hours and then un expectantly hang. The find window \ Find in progress \ Processing query window will appear. The copy cup will then appear. When this happens the database cannot be closed from Filemaker server. The ODBC data source is no longer accessible by other applications. The only way to break the connection is to restart the Filemaker Server.
My configuration is as follows:
Window Server 2016 Standard Edition
Filemaker Server 16.03
SQL Server native Client (64 bit)
Windows 10 Pro 64 bit
FMP 16.03 user connections
Who Viewed the Topic