Hi Mike,

Can't seem to get on the VMP forum so going to follow up on the X3rlb.prg suggestion here on UT.

It has these notes (posting for the benefit of others who might read this):

* X3rlb.prg Copyright (c) 1997-2013 Visionpace All Rights Reserved
* Forces a Refresh of the Local Buffers for the passed ALIAS() (local table), ensuring that a subsequent
* SQL-SELECT/USE ViewName/etc. retrieves the most up-to-date data to this workstation.

* Note that if you open a view or do a SQL-SELECT on a local VFP table from the VMP "report object"
* XXFWMisc.VCX/frmReport private data session, VFP does not reliably get the latest data from disk; records
* added at other workstations on the network don't necessarily show up on the current workstation unless
* you manually update the local workstation buffers with code like this before you do the SQL-SELECT or open the view.

(for non-VMPr's - without repeating the whole function here, the function just places a LOCK on a record in the table and then releases this - somehow this signals to VFP to refresh the data for that table)

Reading the function, it only tries a lock on a table if it is open in the current datasession. But I think this caching is going on because of the same table being open in another datasession (at least I am guessing that) as the report writer runs in its own DS (and the problem is reported as soon as they go into the report writer before any of these tables are opened there). And for these users, part of their startup routine is to open a bunch of the "just about always used" tables in datasession 1 (since opening and closing tables - vfp native tables that is - is slow across the network).

So I am thinking that I need to loop through the open datasessions and perform the x3rlb process wherever one is found.

Thoughts?

Albert