Matt Jarvis wrote: > Jim Harvey wrote: >> What about the set refresh and set reprocess settings, any opinion on those >> base on my other settings? > > Regarding SET REPROCESS I think that all depends on what sort of > technique, if any, you use to deal with file contention conflicts. You > said that mostly you use table buffering = 5, but do you have anything > in place for possible overwrites? >
It all depends on how you access the data too. For example, I don't use buffered tables, but instead use views of buffered (local) cursors of remote data, so the data isn't refreshed until an explicit requery. In the Scheduler app that I posted (or I thought I did...perhaps just screenshots of it), I had a timer that fired in the background the requeried the MySQL web database for the "calendar" updates every 'n' minutes. The purpose in my case was just for visually updating the calendar that showed in the production office, so it was "read only" in that case. Man, that's one of my prouder small apps in terms of GUI in how I pulled it off with good class design and no repeated code: http://mbsoftwaresolutions.com/images/scheduler.png _______________________________________________ Post Messages to: [email protected] 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.
