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,
By Christian Chojnacki
we use your plugin Scribe for editing Excel files in our Filemaker solution.
Since a few days we get an error message when calling the method "ScribeDocLoad" (see appendix) for newer Excel files.
Older Excel files from the beginning of 2018 are not affected.
So we wanted to ask if there might be a problem with the error in Scribe.
We are currently using:
Filemaker Pro Advance version 184.108.40.2062
Microsoft Excel 2016 Ver. 16.0.9029.2253 64-bit
Scribe version 3.08
In the appendix you will find an Excel file that throws an error message when opening with Scribe.
With kind regards
Click to choose files
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
I have a solution running on a Filemaker 16 server. I have accessed the server via VPN on a remote Mac and now want to access the data via ODBC on that remote Mac.
I have turned ON ODBC/JDBC for ALL USERS in the Filemaker file
I have downloaded ODBC Manager – the free version
But when I try access the Filemaker "System DSN" in the ODBC Manager, nothing appears. This is a mystery to me as this exact (and rather simple) setup works perfectly on my local network.
I originally set up the local network some time ago, so:
• Have I missed a step?
• Does the ODBC not work across a VPN as opposed to local network where it works great?
• Does the ODBC manager I am using not work on iOS Sierra?
• Is there something else that I am missing?
Notes: Filemaker 16
Mac OS Sierra
ODBC Manager: 1.0.12