>ISO errors are truly strange. However, I've had a lot of experience with one client who found the problem was in the hardware linking their warehouse computers to the network. Cables and network hardware were getting munched by the heat/cold/damp/dust of an open warehouse. The ONLY errors they saw were ISO errors.
>
>Also, sometimes printer drivers are a culprit. This MIGHT be a possibility for you, since WP may set a different default printer or driver.
>

Another thing that I always check is Network Client configuration, especially if the Novell Client32 is involved. The local caching option is a major source of problems, and the problem can arise if even another station that's working with the same file has it enabled.

Also, since loading another app before VFP seems to clear up the problem, it may be that VFP is creating problems by grabbing up an unreasonable amount of memory for buffering in the absense of any competitors. Playing with the SYS(3050) values and limiting them, especially on NT systems, or on Win9x systems with marginal (<=32MB) physical memory may help. A good rule of thumb for starting values is no more than 1/3 the amount of physical memory installed.