The classic problem I want to solve is preventing one person from writing
over the same record in an update that is being performed on the same record
as another person.
You might be able to get away with only updating those fields which were changed; that way, the second submission only overwrites fields in the first submission if they are both submitting changes. In that case, last entry wins.
This wouldn't work if your data set is such that there are multiple inter-dependant fields. Submission #1 could change Field A to "yes", but Submission #2 changes Field #2 to explain why #1 was answered "no".
--
Ben Curtis
WebSciences International
http://www.websciences.org/
v: 310 478 6648
f: 310 235 2067----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
