ODBC issues with 64 bit applications

Discussion created by lechi001 on May 29, 2016
Latest reply on Jun 9, 2016 by lechi001

Like • Show 0 Likes0
Comment • 6

Hi,

I'm using the FileMaker ODBC driver on Windows to access a FM database via .NET. So far everything works great. The only issue (apart from some smaller ones) is that I cannot run my .NET application in 64 Bit mode as I get a System.OverflowException when I use IDataReader.GetTableScheme() with a table that contains container fields (other tables work). This issue also prevents me from using DSN-less configuration as this works only with 64 Bit for a 64 Bit FileMaker installation. Any help would be appreciated.

Best regards

Michael

Example:

var command = new OdbcCommand(request.Query, session.Connection);

using (var reader = command.ExecuteReader())

{

var schema = reader.GetSchemaTable(); //Throws the exception in 64 Bit only

}

My setup:

FileMaker Pro Advanced 15

Windows 10

FileMaker ODBC Driver 15.00.06.00

.Net 4.5.2

Outcomes

TSGal Jun 6, 2016 1:26 PM

lechi001:

Thank you for your post.

You mention that other tables work, so for clarification, does this issue occur with all tables that contain a Container field or just a specific table?

Have you tried this under 32-bit? If so, do you get the same message?

TSGal

FileMaker, Inc.

Actions

lechi001 @ TSGal on Jun 7, 2016 1:14 AM

Hi,

all tables that have container fields do not work. The issue only happens when I run my application in 64 bit. If I run it in 32 Bit it works for all tables including the ones that contain container fields.

Best regards

Michael

Actions

TSGal @ lechi001 on Jun 7, 2016 7:27 AM

lechi001:

I just want to verify you have both the 32-bit and 64-bit drivers installed on your machine. If not, then please review the instructions on pages 12-15 of the FileMaker 15 ODBC and JDBC Guide at:

https://fmhelp.filemaker.com/docs/15/en/fm15_odbc_jdbc_guide.pdf

TSGal

FileMaker, Inc.

Actions

lechi001 Jun 9, 2016 2:43 AM

Hi,

yes, both drivers are installed and there are DSNs for both that point to the same database. If I run my application as 32 bit it takes the 32 bit DSN, else it takes the 64 bit DSN.

Best regards

Michael

Actions

lechi001 Jun 9, 2016 3:17 AM

Hi,

as an alternative (even the better solution) it would also be possible to use a different approach to read the column Information of a table via ODBC. I could use the method:

OdbcConnection.GetSchema("Columns", new string[]{null, null, "MyTableName"})

This Approach works with tables and indexes but unfortunately for columns this gives me another exception:

A column named 'SQL_NO_NULLS' already belongs to this DataTable.

Could you check if the mentioned column really is duplicated by the ODBC Driver?

Best regards

Michael

Actions

lechi001 Jun 9, 2016 6:40 AM

Hi,

I finally found a workaround for the issue. As I am only interested in the column names and the data types I now use the following code which works for 32 bit and 64 bit:

var command = new OdbcCommand(request.Query, session.Connection);

using (var reader = command.ExecuteReader())

{

for (int i = 0; i < reader.FieldCount; i++)
{

var dataType = reader.GetDataTypeName(i);

var name = reader.GetName(i);

retVal.Add(FMField.Create(name, dataType, i));

}

Best regards

Michael

Actions

6 Replies

TSGal Jun 6, 2016 1:26 PM
lechi001:

Thank you for your post.

You mention that other tables work, so for clarification, does this issue occur with all tables that contain a Container field or just a specific table?

Have you tried this under 32-bit? If so, do you get the same message?

TSGal
FileMaker, Inc.
Like • Show 0 Likes0
Actions
lechi001 @ TSGal on Jun 7, 2016 1:14 AM
Hi,
all tables that have container fields do not work. The issue only happens when I run my application in 64 bit. If I run it in 32 Bit it works for all tables including the ones that contain container fields.

Best regards
Michael
Like • Show 0 Likes0
Actions
TSGal @ lechi001 on Jun 7, 2016 7:27 AM
lechi001:

I just want to verify you have both the 32-bit and 64-bit drivers installed on your machine. If not, then please review the instructions on pages 12-15 of the FileMaker 15 ODBC and JDBC Guide at:

https://fmhelp.filemaker.com/docs/15/en/fm15_odbc_jdbc_guide.pdf

TSGal
FileMaker, Inc.
Like • Show 0 Likes0
Actions
lechi001 Jun 9, 2016 2:43 AM
Hi,
yes, both drivers are installed and there are DSNs for both that point to the same database. If I run my application as 32 bit it takes the 32 bit DSN, else it takes the 64 bit DSN.

Best regards
Michael
Like • Show 0 Likes0
Actions
lechi001 Jun 9, 2016 3:17 AM
Hi,
as an alternative (even the better solution) it would also be possible to use a different approach to read the column Information of a table via ODBC. I could use the method:

OdbcConnection.GetSchema("Columns", new string[]{null, null, "MyTableName"})

This Approach works with tables and indexes but unfortunately for columns this gives me another exception:

A column named 'SQL_NO_NULLS' already belongs to this DataTable.

Could you check if the mentioned column really is duplicated by the ODBC Driver?

Best regards
Michael
Like • Show 0 Likes0
Actions
lechi001 Jun 9, 2016 6:40 AM
Hi,

I finally found a workaround for the issue. As I am only interested in the column names and the data types I now use the following code which works for 32 bit and 64 bit:

var command = new OdbcCommand(request.Query, session.Connection);
using (var reader = command.ExecuteReader())
{
for (int i = 0; i < reader.FieldCount; i++)
{
    var dataType = reader.GetDataTypeName(i);
    var name = reader.GetName(i);
    retVal.Add(FMField.Create(name, dataType, i));
}
}

Best regards
Michael
Like • Show 1 Like1
Actions

ODBC issues with 64 bit applications

Outcomes

Related Content

Recommended Content