Access to FileMaker : strange behaviour from ODBC link ?

Creating desktop or client-server database solutions?

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
bangkok
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 937
Joined: Fri Aug 15, 2008 7:15 am

Access to FileMaker : strange behaviour from ODBC link ?

Post by bangkok » Sun Sep 13, 2009 4:15 pm

Hi,

I have 2 System DSN, for ODBC, pointing each to a local FileMaker file : DB1 and DB2.

Both databases are linked together but within FileMaker.

When I open a connexion with RunRev though ODBC to DB1, but with a SELECT query targeting a table from DB2 it's working !... And it's working even though I close the Filemaker file DB2.

How ODBC can "guess" that links exist between both Filemaker DB files, and act accordingly ?

I should receive an error : because the table name I use in my query does not exist in the DSN I use ?

bangkok
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 937
Joined: Fri Aug 15, 2008 7:15 am

Post by bangkok » Sun Sep 13, 2009 4:22 pm

Ok, mystery solved. :D

I should have thought about it.

Actually, it's not related to ODBC... but to FileMaker.

And more specifically, to the "File references" (menu File/Define)

In DB1 there is a "file reference" to DB2... therefore Filemaker can pass the query to DB2, sent by ODBC.

(those "file references" are used to create "relationships" with other tables from other files.)

If I delete this "file reference", then the ODBC driver displays an error :" Error in column...." etc.

Post Reply

Return to “Databases”