>We are attempting to print VFP6 reports to pdf files using Acrobat 4.0 on Winows 98. When we write a report to pdf, the computer crashes and must be rebooted. The pdf file gets created but, when control returns to VFP6, the system blows up. The only thing we can figure is that Acrobat steps on VFP6 memory while it is doing its work, which destroys the VFP6 in memory. Is there any way to isolate Acrobat 4 or VFP6 in its own memory space?

This may be a problem similar to that seen with some HP printer drivers (C5 errors); the only thing I can suggest is that if you have not applied VS SP3 to your VFP, try that, since it addressed a number of C5 errors, including pritner drivers that didn't reset the FPU properly.