Michael, By on demand do you mean you added a button the user could click to refresh the data?
If that works from your experience maybe I should do that instead of the timer. I've had a timer running on one form for awhile, with no ill effects, but if I add the same to more forms, it may develop into a problem with traffic, as Rick mentioned... James E Harvey Hanover Shoe Farms, Inc. M.I.S./Corresponding Officer Off: 717-637-8931 fax: 717-637-6766 email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MB Software Solutions General Account Sent: Friday, October 03, 2008 11:23 AM To: ProFox Email List Subject: Re: updating data on multi-user form Rick Schummer wrote: >>> Thanks Rick, it was the SET REFRESH setting I was missing. As soon as I > changed it to 5,5 from 0,0 the form data refreshed.<< > > Please note the lower the number the higher the network traffic you will introduce. Set wisely. > > Rick > White Light Computing, Inc. Good point. That's why I prefer a separate data set locally (e.g., views/cursors) and then only requery on demand. That data access strategy has never failed me, and once I changed over to that design, I got past many data "anomalies" with just using buffered vfp table data. [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
