>You're being eaten alive by data buffering; in all probability, you need to limit VFP's voracious appetite for RAM in the effort of having it not force things in and out of the swap file; about the worst scenario you can construct for VFP is where several copies of VFP are up at one time, each tries to grab 50-80% of the total system memory (that's V+R) and so the ones not at foreground swap out. Task swwitches, and shutdown where buffers have to be rewritten require that RAM get cleared to let you swap stuff back in so it can get written to disk. Look at the SYS(3050) as a means of controlling how much memory is used for buffering by VFP in foreground and background execution.

I am having a similar problem at a client site. The application shuts down for me instantly but for them can take a couple of minutes. I would like to try SYS (3050) to see if it helps. Are there any rules of thumb as to what it should be set at? Or is it just trial and error?