Barbara, Ed, et al...

"Wait a second", I thought after typing out my latest reply to Ed. His mention of views and tables caught me in a moment of psychic euphoria. I completely forgot, but we are NOT using Views at all. (Don't ask why. As a little history, this is a migration of a FPW2.6 system and the decision was to reduce the time to migrate and not make many changes - hence our using the tables directly and not views).

Anyway, this is still a weird issue/anomaly. What I think may be happening is that the data from the table is being cached or stored in memory and that is what the SQL statement is grabbing when it builds the array. As I stated, when I close and then open the table, the SQL statement builds the array with the latest edited data. It seems that just modifying an existing field is not causing this data buffer to become refreshed whereas the addition of a new record is causing this to occur without a problem. The table has relatively few records 20 to 30 maybe. I am wondering what will happen if I just move the record pointer? Maybe that will cause the buffer to refresh? Or, is there any other way to cause the cached data to refresh?

...douglas