>The best example I can give is one I'm curretnly working on. The thing is is that the tagbles I'm working with are no samller than 600 meg up to 1.4 gig.
>
>After I message the table, I close it and pass over control to another application that then works on the table. The loop I wrote before is the loop that I use in VFP5 to keep th code from progressing. I have noticed up to a 5 second pause after the other application has completely closed down that VFP is able to again open the table.
>
>When using the copy cammand I also have found that size has a definite affect on how the code runs and how the OS takes it time to completely release the table.
>
>These experiences occurred while working on a WindowsNT and the tables located on my hard drive.

Sandy,

I see, thanks for the info. I have never done exactly what you are doing before. I have often created tables with "copy to" and then imediatedly used the table in procedural code. I have not launched another app which would intern try to use the table. Something to look out for.

Best Regards,
Mike