Hi Ed,

Have not delved into the registry setting yet but gonna try that in a few minutes. I *did* insert code though to close and then reopen the table just before I did my SELECT query and this indeed seemed to solve it. But given that in all my years of FP/VFP work (10+) everything we were taught was to open tables and keep them open, this seemed like a kinda brutal solution. I guess though as long as VFP doesn't mind opening and closing the table every 5 seconds (and it shouldn't), it would be a reasonable solution.

I am going to try the registry settings next - I always figure it is better to go after the source of the problem than to insert a kludge to work around one.

Thanks,
Albert

>You may want to play with the registry settings for Optimistic cache buffering and NT caching; there have been several threads regarding these settings on the UT over the past month or two, so I'd suggest searching the message base.

>The indexes are updated whenever a TABLEUPDATE() is submitted that changes the content of a tag field; writing some data does nothing except creating a dirty buffer, impacting system throughput for all users. If you want to cause a re-read, force all inastances of the table closed (including views and base tables) and then open the data in a new data session; this is about the best way of ensuring that the data is fresh if you suspect that there's a local caching issue in the works.