>>But perhaps you are asking how to allow someone to edit data without being overwritten by someone editing the same data.
Well, this is exactly what one would call a "race condition", isn't it ? >>Sally's update has overwritten Bobs Exact, this is actually what should be avoided in any database application. Happily, it does not happen too often, unless the application has a large number of users. >>To solve this problem we need a table or session or application variable holding "checked out" records. The use of application.cfc is useful here because the "onsessionend( )" function can be used to "clean up" locked records that are orphaned by someone going out for pizza or pressing the red "reset" butto non their PC. How you do it depends on how complicated your DB schema is, and how granular you envision your locking scheme. Just what I thought, there is not tool available for this, neither in CF, nor ODBC, nor SQL. This is just unbelievable, now in 2006 with the database systems we have! This what so simple in 1980's, with dBase, clipper, Foxpro you name it, under DOS. All had Rlock() and Flock() functions. Rlock() was used when editing a record, Flock() locked the whole file, for instance while indexing a table. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252360 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
