>Bela,
>
>You can lock, then unlock the file, then do the SELECT. This will ensure that the data is up to date at least at the point where you unlocked the file. If you need to make sure nothing changes during the SELECT, you'll need to lock it while you do the SELECT. Here's an example of unlocking before the SELECT:
>
>IF !FLOCK()
> WAIT WINDOW NOWAIT 'WARNING: Data may not be up to date'
>ELSE
> UNLOCK
>ENDIF
>
>SELECT * FROM ...
>
>Hope this helps.
>
>Josh
>
>>Hello Everybody!
>>
>>I have an always open, (multiple instances opened) network table.
>>I saw and read here in UT, that Locking the file will ensure that VFP
>>read the most current data directly from the network file instead of its internal cache. But I use select-sql commands, which can last for 20-30 seconds, and I donnot want to lock the file so long.
>>Is there any way, to ensure, that VFP reads the phisical network file, instead of its internal cache, without locking the file?
>>
>>TIA
>>
>>BB

Hello Josh!

Thanx, it works great, as I wanted.

When I thought about this problem, I got a thought:
I am wonder, how could VFP do local caching, when local storage space could be less, than network files size?

BB