On 1/18/2012 6:19 PM, Kent Belan wrote: > Both old and new apps are have buffering set to 3 on all tables. > > I have coded the new app to close the table just after the save and just > prior to the load. > > I thought this would clear the buffers and write the data to disk but the > old app still pulls the old data
I saw long ago advice that said to always use TABLE buffering (5) instead of ROW buffering (3). Just a tip. Reasons were that row buffering sometimes left you with intended consequences (like commits on row changes) and perhaps something about performance too. (Makes sense, if you think about it.) Is the data being committed with a TABLEUPDATE explicitly? -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ 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/4f175544.4040...@mbsoftwaresolutions.com ** 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.
