Clicking Save and closing the form does not guarantee VFP buffers have been flushed. A starting place is to add FLUSH command every place data is saved (INSERT, UPDATE, DELETE). FLUSH will go after the actual data update statement.

>My code does not have any FLUSHs in it. And in this case, the person running the report (the "salesperson") does not enter in the data - that is done by back office staff. The sales people like to run their reports throughout the day (particular at month end :-). But they are not entering the data.
>
>I am pretty sure that the person entering the data would have closed the form (and saved) much earlier in the day. Here was the example I tracked down today:
>
>- one sale entered with a timestamp of 12:01 pm (each record is timestamped when saved)
>- another sale had a timestamp of 1:02 pm
>
>When I logged in to run the report (at 1:30), I got both sales on the sales report
>
>- when the user who called ran it, he got neither sale showing up (I checked and he logged on at 11:15 am)
>- I had him run the report from another user's PC and they got one of the two sales; I checked and she had logged in at 12:36 pm
>
>So that makes sense - she got the sale that happened before she logged in but not the one after.
>
>I would have thought that there was something in VFP that when a query is run, it checks to see if there has been any changes to the table since the last time it opened it and if so, it refreshes its data.
>
>To me the weird part is that if the user runs the report again right away, they get all the data - it's like on a 2nd run VFP decides to pull down the latest data.
>
>Thoughts?
>
>Albert