4gl problem
Posted in 1993
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? Here is the structure... first the data is fetched into gr_client.* and gr_cladd.* for the simple purpose of the select only. then I declare an update cursor for both with hold and for update. I issue a begin work. I open these cursors and fetch them into the gr_client.* and gr_cladd.* variables. Then I do an input by name without defaults on each column in the order they appear on my form. Next I have an update client and an update cladd statement followed by the lock_cursors being closed and then a call to my display_client call which simply displays gr_client.* and gr_cladd.* on the form again.... BUT.... why is the updated data not displayed when I do a next then a previous?? Am I missing a step in making my gr_ variables equal to the data just inputted??? PLEASE HELP! -- -john@nteltec.com,john@jcm.com Opinions expressed -John C. Musselman are mine and (but we can share -National Tel-Tec Inc. mine alone...... if you like....)