Hi Allen > Message: 2 > Date: Thu, 26 Jul 2007 12:39:31 +0200 > From: "Allen" <[EMAIL PROTECTED]> > Subject: RE: Write ahead cache problems > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="windows-1250" > > Hi Paul > This is what I feared. Its not too good when two products by a very large > company don?t work together. I had hoped it might be fixed by VFP9 but seems > not.
I don't think it's reasonable to expect every aspect of networking to be compatible with VFP. The network guys need to understand that write caching is applicable to a single user updating a single file (file server). It is not good for multiple users accessing a single file, as happens with each DBF and CDX (file sharing). I sent this article to the network guy and he's agreed to come in and make the change just to be safer. http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html#Do%20Coding%20Practices%20Affect%20These%20Issues? However, I have a system based on Visual MaxFrame Professional running on a server with write caching on and it's behaving perfectly. Mike _______________________________________________ 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.
