Embedded SQL Statement Caching Records???

["Gordon R. Robinson IV" <GRobinson@xxxxxxxxx>]

I've written an embedded SQL RPG program where I read 10 records to fill in
my subfile.  The user can select a record and modify the information with a
call to another program.  When the editing program returns control back to
the SQL RPG program I have it reread the last ten records to "refresh" the
data on the screen, since it might have been modified.  However, the SQL
program seems to be getting the old information like it was caching the
records and just retrieve the cached information.  The only way I can get
the information refreshed is by running a different SQL statement (one that
is ordered differently or has different Where conditions).

Does anybody know if this is true?  If so, is there a way to turn it off?
Or better yet, is there a way to force it on specific instances to read the
actual data?

Looking through the archives I found some talk about "with NC" and "Dynamic
Scroll".  I tried adding these to my program, but they didn't seem to help.
Any thoughts?

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---