> Can you explain more about database flags and how they may come in handy?
>
you might do something like this. For all tables (hmm other than transition
tables that implement many-to-many relationship, tho even there you could
bother to do this), include some additional fields, consistently named
throughout your DB, for example
Active_YN
CreatorID
CreatedDateTime
ModifierID
ModifiedDateTime
with their obvious meanings. You might already be doing this part.
THen, in the data <form> from which the user puts in data, include a hidden
field, perhaps called FormDateTime which is set to #now()#. Now, (no pun
intended), normally on the action template you'd be seting the
CreatedDateTime/ModifiedDateTime to #now()# anyway--but by passing this
along from the form page, you can consistently check to see if the "now"
your using for *this* update is different from the "now" you'd used at the
last update. If they are the same then the form was submitted twice,
otherwise the form page would have a "now" which was different. DOn't let
the "current time" english language meaning of "now" stop you from seeing it
only as a variable that can be captured as of the moment that a CF template
calls the function :)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
