Hello
We have frequently observed this error. We are curious if 360Works knows if this has been fixed in FMS 16.
We are interested in knowing if there is something about the content of the records this affects that we could avoid while retaining the JDBC sync. Also interested if, or how much, switching to XML affects the client's sync. Duration only I suspect. I'd assume the switch to XML is a 'server side' change only and does not require a client update. Let us know if that is incorrect.
• update operation for table FileMaker Server xxxxx failed for target nodeId '1B207AE7-4063-4BF9-B450-62522235B189'.
A bug in the FileMaker JDBC driver prevented record '1B207AE7-4063-4BF9-B450-62522235B189' from Client node xxx on xxxx from being written to FileMaker Server xxxx. You can delete this record and retry the sync, or you can switch to XML for the sync. Please report this problem to 360Works so that we can forward it to FileMaker. [1 more warnings like this]
Thanks, Mark