I'm looking for help on the best way to handle a conflicting change scenario in my database
In the database, there are 3 users that have the ability to export a list of jobs, make changes and import that spreadsheet again -- everyone else can only see the forms/ reports. This (I believe) is going to be where most conflicts appear.
The reason they need to export & import the list, is due (in part) to the way in which invoices are received from our contractors - they send a list of jobs they've completed as a spreadsheet, which is then compared to our entire list to see if it's been paid.. the format of these spreadsheets vary to a large degree.
I'd rather not implement a record lock on the form, as that would then rely on the user to check that their changes were applied.
What other options are there?
In the database, there are 3 users that have the ability to export a list of jobs, make changes and import that spreadsheet again -- everyone else can only see the forms/ reports. This (I believe) is going to be where most conflicts appear.
The reason they need to export & import the list, is due (in part) to the way in which invoices are received from our contractors - they send a list of jobs they've completed as a spreadsheet, which is then compared to our entire list to see if it's been paid.. the format of these spreadsheets vary to a large degree.
I'd rather not implement a record lock on the form, as that would then rely on the user to check that their changes were applied.
What other options are there?