The problems (note plural), fall into two categories:

1) Issues with printing caused by some printer drivers coming up with "Pure Virtual Function Call", then failing

2) Issues caused because someone decided 6 years ago to do a functional conversion of the system from FoxPro 2.6 for Windows into VFP6. The source code for this was a conversion itself from a DOS product. Consequently, we have few classes, no forms, no VFP reports and basically a pile of smelly stuff.

I'd rather find another job than fix all of this, which is inevitable if the owners decide to ship the VFP development environment.

Simon