Does Dynamics not have sql syntax that will roll back a transaction? We run in a citrix environment with 6 locations all accessing a central server. If a disconnect happens and it does not reconnect, the user must delete themselves out of Dynamics and if they were working on a SOP invoice, those items are STILL allocated and we are running into MAJOR problems during counts.
Why does Dynamics allow such major data corruption? Should the data NOT be written to the actual table until a COMMIT is reached? Temp tables should be used, then committed to live tables when a save is done.
Why does Dynamics allow such major data corruption? Should the data NOT be written to the actual table until a COMMIT is reached? Temp tables should be used, then committed to live tables when a save is done.