I guess this is a valid PFC question -- I am trying to build persuade argument to convince my boss with should convert our application to use the PFC and its LUW and Linkage services. I have a database question asked from the point-of-view of the application developer -- perhaps someone can help settle a debate among our team members. Is there anything "wrong" with "hanging updates"? Are there good reasons to avoid their use? What problems are associated with them? Could a hanging update cause a deadlock? "Hanging updates" is the term I use to describe the situation where, say in a data-entry scenario, the user completes one part of the data-entry process (say data-entry for one table) and a update to the database (for one table). But no commit is issued because only the first step is complete and might have to be rolled back should any of the subsequent processes in the logical unit of work (LUW) fail. Lester LaForce [EMAIL PROTECTED] Sr. Software Developer (Contractor) Future Technologies, Inc. Armed Forces Institute of Pathology Washington DC > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
