>Thanks for the response Ed.
>
>What I am told is that the NT virtual memory available throuth the NT network is allocated to each of the workstations on the network. The amount of virtual memory that was originally assigned to each workstation shrinks as times goes on. They need to reallocate virtual memory about every two weeks.
>

Something doesn't ring true here; either you aren't describing the problem in detail, or I'm misunderstanding what's involved.

Each Win32 system's virtual memory, NT or not, is allocated at the local station. Are you stating that there is a loss of available virtual memory on each station? That would indicate some sort of memory leak within Fox 2.6, such that some memory allocated to a Fox 2.6 session would not be recovered by the operating system. I'm not aware of such (doesn't prove much, since i haven't been dealing with FPW 2.6 in an NT production environment). From NT's perspective, since FPW 2.6 is a 16 bit application, the effect could be minimized by running each instance of FPW 2.6 in its own Win16 VDM, which would create and destroy itself, releasing all the resources of the VDM back to NT.

If you're saying that there is a per connection loss at the server end because of FPW 2.6 applications running on client boxes, I'd be extremely surprised - FPW is not running on the server, and can't directly allocate virtual memory on the server.

If you can give a more concrete description of the problem, maybe someone else has some experience with the problem your client is reporting.

>The clients hardware person who is responsible for the network talked to someone from MicroSoft at ComDex and was told about a potential problem between FoxPro windows vs. 2.6a and the NT network. I am not up on networks or NT so I am not sure what is going on.
>
>bb