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 ?
Access to FileMaker : strange behaviour from ODBC link ?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Ok, mystery solved.
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.
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.