Re: Transactions and Record Locking Help Needed

: In article <43a33d$m7o@newsbf02.news.aol.com> : billkuruc@aol.com "BILLKURUC" writes: : > We are implementing transactions into our standard engine database. : > We have many programs that have header/detail data where user is entering : > a header, then numerous details. Currently we lock header with "select : > for update" statement and keep it locked while all other details are : > input. Then at end we free up all locks. : > We understand that if we use transactions and "commit" a detail line, we : > will lose ALL locks, including the header lock, which would then allow other : > users at data which we do not want them to get at while its being updated. : > Is there any way to stop other users from updating the same header and : > detail data automatically ? We discussed setting "header in use" field : > manually, but this requires us to write recovery code logic if a process : > fatals and "in use" flag remains set when its really not in use. : > We are thanking you in advance for any suggestions you can provide !!!! I'm facing exactly the same problem as you. There must be some C functions (maybe with semaphores ??) to handle the problem without conflicting with the lock put by the SE. Somebody out there must have some solution. Luc Chatelain ogc@cam.org.ca