We are using a SQL Server 2012 backend for our software. Right now I'm trying to improve our orders form, where an existing order might be opened, modified, then saved. When it is saved, several updates, inserts, and deletes may take place on several different tables during the transaction.
What I want to do is ensure that, since this form may be edited over a period of several minutes, that it won't save over someone else's modifications. If there are differences in any of the tables (shipments, payment, etc), the user will be notified and that section will update in the form instead of saving. We're using Windev 18 for our front end, which is having trouble reading the timestamp field.
I've been trying to compare all the relevant fields for differences before applying the modifications, but this takes 1-2 seconds, and I'm worried there could be saves in between. I researched rowlocks, but apparently they could be escalated to a tablelock if there is high volume-not sure how that would affect our system.
Any advice for going about this?