Hi Mike,

How are things?

I am in total agreement that this is a VFP issue. This is an issue I have been struggling with for some time now. I keep going away from it and hoping it will just disappear, but unfortunately it keeps rearing its ugly head :-)

In fact I discussed this very issue with you about a year ago regarding reports and have since changed all my reports to run a method that issues an x3rlb() for every table in the report.

The only reason I mentioned Maxframe in the first place is that I was hoping someone else using this framework might be able to suggest the best way to handle this in a base class and take into consideration the default way that Maxframe opens all tables at app startup, etc.

Paul

>Hi Paul
>
>Its been a long time! Issuing an rlock may cause a refreshing of the data on my workstation, but it wouldn't help when a user on a another workstation added a record. This isn't specifically a MaxFrame question, its a Foxpro question. If you're using views, the views won't show new records until a requery is issued.
>
>I'd try to reproduce this problem without MaxFrame first. Then try to issue an rlock or an unlock and check reccount() or something. Don't use browse since it has its own ability to get recent changes, via SET REFRESH.
>
>>I have a commercial app developed in VFP 6.0 and Visual Maxframe. I have many clients that complain of records input on one workstation don't show on the other workstations for a delayed period of time.
>>
>>I have done a lot of research on this and have come to the conclusion that I need to change my base form classes to issue an rlock() on all open tables. Is this a correct conclusion? Is anyone else doing this?
>>
>>I was wondering where would be the best place to put this code. Would it be in the init of my base form class?
>>
>>Any better solutions?
>>
>>TIA
>>Paul Acton