Ted
Thanks for your input. If I issue USE DBF('tmpctran') AGAIN ALIAS TEST IN 0,
FILE(DBF('tmpctran')) still returns .F.
Richards answer was quite informative as the behaviour DOES depend on the size
of the cursor created by the SELECT statement, irrespective of the READWRITE
clause.
Paul
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Ted Roche
Sent: 05 January 2016 19:47
To: [email protected]
Subject: Re: Odd/inconsistent behaviour of DBF()
On Tue, Jan 5, 2016 at 11:35 AM, Paul Newton <[email protected]> wrote:
> Richard
>
> I used the NOFILTER clause and a physical file was NOT created ...
>
> Paul
>
I believe that FoxPro aggressively caches both reads AND WRITES so the TMP file
is probably not created unless it has to be. A small DBF takes little space in
RAM and can be accessed in nanoseconds, while a file written to and then read
from takes takes milliseconds. If you USE the file and then go look for it, is
it flushed to disk at that point?
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.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.
