Re: 4gl problem

John Musselman writes: > My Prob: The date is updated, BUT if a user updates a row and the does a next > followed by a previous (fetch_next and then a fetch_prev) the data displayed is > the OLD data... but if the user selects the same row on a subsequent query, it > refelects the changes. Why must the data be re-selected? Your problem can be solved by using two cursors. You need to declare the first cursor for the given criteria and store only ROWIDs of the selected rows. Based on these rowids you declare another cursor to get required columns. This approach will ensure that you always get the most current data. Alternatively, you can SET ISOLATION LEVEL TO COMMITTED READ. But to use this isolation, you have to COMMIT WORK to release locks placed by the update process, as this isolation does not return a row that has not been committed. Regards. -Rajhans. -------------------------------------------------------------------- Rajhans G Tawde Internet: raj@shack.csci.csc.com CSC Intelicom Voice : (303) 643 1476 116 Inverness Drive East Fax : (303) 792 0319 Englewood, CO 80112 Standard Disclaimers Apply. --------------------------------------------------------------------