>>
>>OK. Just a reminder - it's windows XP. fsize did the same thing as ADIR. Trying FOPEN next, but switched from that originally because of a suspected deadlock situation.
>
>Note that I said "fopen() read only" - and that'd be unbuffered as well. Since you aren't exactly reading anything, just doing a ?fseek(h, 0, 2) shouldn't hurt. I'm trying it with a similar process as I write this, and it seems to work, though the example is wrong - it's too fast and was finished before I could check whether it's reporting progress or not.

FOPEN(m.lcFile,10) always reports -1. The file is being created by SQL Server - probably exclusive use.

If was only ever able to use FOPEN as a means of checking if the file had been completely created. Until we ran into what looked like a deadlock.