Re: 4gl problem

In article <CInMq8.C5q@news.direct.net> you write: } I have 4gl 4.00.UC1 for Interactive Unix... I am having the following problem. } } I have written a module that queries from 2 tables (using an outer join) with a } scroll cursor. The user (after querying) can then update one of the rows that } are returned by using fetch_next and fetch_prev. } } 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? } What you might want to try is this... First declare a scroll cursor that selects just ROWIDs based upon a user's search criteria. Next declare an update cursor that selects the actual data based on the ROWID from a fetch of the first cursor. You'll be using the scroll cursor to do your next and previous movment and the update cursor will guarantee that your data is always current. This was the approach I took in the very first release of db4glgen. I've since gone with dynamic memory management of rowids. DAS -- David Snyder @ Snide Computer Services - Folcroft, PA Current Release is db4glgen-3.17 UUCP: ..!uunet!das13!dave INTERNET: dave@das13.snide.com