FileMaker is not a SQL-based database. ODBC drivers for FileMaker attempt to emulate SQL functionality, but there are limitations due to the fundamental differences in how the two platforms handle data. For example, FileMaker has no separate data types for integer versus real numbers.
Instead of pushing the records from Access to FM, I recommend running an import on the FIleMaker side via an ODBC connection to the Access database. You will have a lot less trouble, because FileMaker will automatically do some conversions for you that you otherwise would have to do on the Access side.
Main Topics
Browse All Topics





by: lesouefPosted on 2009-11-03 at 08:34:45ID: 25730710
First, the "not empty" (=null) condition can be removed in the fm db, at the field definition level, in the validation tab.
Second, imports can be done with capture mode on, this way, errors should not be reported, but 1st way is of course better.