>Hi Mike,
>
>Thanks for the response. I am going to re-post this because re-reading the docs once again, I realize that my problem is slightly different than what is noted in the docs.
>
>I found that X3RLB does indeed solve the original problem I had with data *from another workstation* not showing up in a report - so I implemented that and it worked. But I am having trouble with data not showing up that is posted by the same user i.e. post data via a form, then user reopens a bit later and data not there (only child data it seems, weird).

In frmData of xxfw.vcx method UpdateBuffers have a look at the comments regarding FLUSH.

>
>Albert
>
>>Hi Albert
>>
>>Sorry for taking so long to get back to you. The docs on x3rlb says calling it before every query should work. That sounds like overkill though.
>>
>>>Hi Mike,
>>>
>>>I am having to cycle back to the X3RLB discussion (for a different problem). A few users have reported that they sometimes have missing rows in a form if they enter the data, then exit the form, then go back in a few minutes to change something. It usually seems to be child records of a form. Note that this is all with native VFP tables, no SQL etc.
>>>
>>>I thought of using the X3RLB program to force a lock on the tables thus hopefully forcing a refresh of the data.
>>>
>>>Question: if this table is open in multiple data sessions, do I need to force a refresh for the same time in each data session or would it suffice to force it in just the first datasession where it is found (if you know). It seems to me that doing it once would suffice but don't really know.
>>>
>>>Thanks,
>>>Albert