2 Replies Latest reply on Nov 3, 2010 10:35 AM by TSGal

    FileMaker Go does not always commit data properly on a local network

    fabricen

      Summary

      FileMaker Go does not always commit data properly on a local network

      Product

      FileMaker Go

      Version

      1.1

      Operating system version

      iOS 3.2

      Description of the issue

      Several customers reported that when committing a record in FileMaker Go, it seems saved properly (they can go to another record, go back and see their new data) but it's in fact not pushed to the server.
      This issue occurs only on a local network, never on a WAN.
      I'm surprised this has not been fixed in the past upgrades (or at least not documented). It seems rather critical in terms of centralized database.

      Note : I don't know if this has been reported before, but finding something on the forum has become challenging, to say the least. Even if you go to a product specific forum (FileMaker Go in this case), results would point to any forum. "Go" is not accepted as a search key because it is too short, event in "FileMaker Go" (with quotes).

      Steps to reproduce the problem

      Commit a record, check from FileMaker Pro : no changes

      Expected result

      well, it would be nice if the data was saved!

      Actual result

      The data is not saved on the server.