>Has anyone had a problem with an FoxPro 2.6a app running in an NT network (app being on the server and workstations accessing the server) where the virtual memory is not released when the 2.6a app is terminated? It appears as though virtual memory is growing eachh time the 2.6a app is run, but not sure that 2.6a is the only culprit. Is there a work around or something that can be done within the 2.6a app to release virtual memory when the app is terminated.
>

By not releasing virtual memory, do you mean that the swap file is not shrinking on the NT box? The size of the swap file doesn't necessarily shrink although the free areas of the swap file will be reused by other processes on the NT box.

>Thanks for any help.
>
>bb