>SNIP
>>
>>Is there any reason the FileToStr()'s couln't be wrapped in an FLock() - at the moment I rely on a SQL Select relying on a DateTime stamp to pull out Updated / Inserted rows. This is very quick and I'm not sure it's worth investigating the FileToStr() alternative.
>
>Just FYI, Houston... I've found that a STRTOFILE() is about the only guaranteed way to get an UNfragmented .FPT.
>That is to say, a FPT that is the result of a COPY... or a PACK MEMO remains a fragmented file but a .FPT that is STRTOFILE()ed will have only a few fragments dependent on the RAM cache available and the size of the FPT itself.
>
>For what it's worth...
>
>cheers


Hello Jim.

Interesting. On large FPT's would a 'rewrite' in such a way speed up the reading/processing in a regular app because it is now not fragmented anymore?

this would be something worth putting into a table maintenace module of an apps ion to index/pack.

Update:
How about the dbf and cdx files, are they fragmented as well?