2 Replies Latest reply on Jul 28, 2010 8:48 AM by TSGal

    ODBC Insert does not trigger auto-entry into global field

    giddiv

      Summary

      ODBC Insert does not trigger auto-entry into global field

      Product

      FileMaker Pro

      Version

      11v2

      Operating system version

      MacOSX 10.6.4

      Description of the issue

      Using ODBC to insert the first record of a table that has a data (or calculation) auto-entry into a global field yields a new record in which the global field is not set.

      Steps to reproduce the problem

      1) Define a table with a global field that is Global, Auto-enter Data. Add another non-global field.
      2) Allow ODBC Sharing.
      3) From an ODBC client, insert into the table and set the other non-global field.
      4) examine the result, the global field value will not be set.
      5) However, adding the record "conventionally" (New Record) will set cause the global field to be set.

      Expected result

      That creation of a record in the table, either through ODBC or New Record will cause the global field to be set to its auto-enter value.

      Actual result

      The global field will not be set despite the creation of a record in the table.

      Workaround

      None