We found that the problems occurred when another rbase session or other program (via oterro?) added or updated data in the target table. Our form would not see the change. If the code in the form made the insert/update then there was no problem.
Hope that provides some "Blues Clues" Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, March 31, 2011 11:38 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: CSV and Null unload question Really? Any update at all? I wish, however, we could identify those situations where a "select into" (that was the only command I had problems with) usually works but rarely doesn't. If there happens to be any update command in the program before the "select into" then apparently the command will go to disk rather than cache. But since 99.99% of my select into's have had no problems, I can't imagine it was because all of them had an update right before... Strange. Karen We did some testing and updating ANY table clears the cache, even an update to a temporary table! Dennis McGrath
