>I have been developing with FoxPro 6 for about 6 months and I'm still not sure if I'm using cursors correctly. My main use of FoxPro is for creating DLLs that are used in Internet applications.
>
>At the end of my procedures and functions I am issuing a CLOSE DATA call that I think is closing all Cursors. Since I do not use the USE command, instead acessing all my data through SELECT statements and using the INTO CURSOR command the CLOSE data should release the cursors memory.
>
>The part that bothers me and this my be normal is that I have to shut down the web server to get exclusive access to DBF files. What is FoxPro doing with the SELECT statements that causes the DBF files to be unlockable as exclusive? (Assuming that there is no activity on the web server but a instance of the COM object has been created.)
>
>It is just that the FoxPro developer I work with that does Windows development is annoyed by having to stop the webserver to get exclusive access to the DBF files. Any advise?
>
>Tadd Bryan.


CLOSE DATA will close your cursors and tables. Stopping the web server is not a FoxPro problem, but is due to running the DLL in IIS. Run the DLL in MTS and then you only have to shutdown the package running the DLL.