Current setup is Windows Server running FMS 11 with 10 Mac clients.
FMS 15 is on the way - final hoop-jumps next week.
The server is in-house as are clients so FMP performance is not at issue.
The main database has an ESS connection to a SQL db in Texas (we are in Alberta).
Things work well 99% of the time.
It is the 1% that is becoming problematic.
We have a number of routines that push data into the SQL tables (these tables sit under client website) and load course registrations.
Sometimes we lose contact mid-routine and the user gets stuck with an "ODBC lost connection..." error message that can only be cleared by a ForceQuit of FMP. Suspect that the record we were writing to in incomplete wrt mandatory/non-empty fields.
Is there a reliable way that we can detect the connection loss during a routine? eg. Get(ODBCError).
I suspect we could drop in a Revert Record if we knew the connection was lost - though without the connection I am not sure the revert would revert.
"Shuffling is the only thing which Nature cannot undo." ~Arthur Eddington