>Hi George, thanks for the quick reply
>
>>
>>I doubt that VFP is the direct cause because the DLL in question is a 16 bit DLL. Are there any 16 bit apps running when this occurs.
>
>No. This is on Windows 98, if that helps at all. There's nothing running on the PC at the same time as my VFP exe.

>Just thought - could it be the printer driver [wondering if this is a 16-bit printer driver] ? I'll try switching to a different printer when I get back to the office tomorrow morning.
>
>Best.
>
Hi Matt,

I'm thinking the same thing. Toolhelp.dll is a 16 bit DLL that ships with NT and 98 (I don't know about 95, I'm running 98 here, but I'll check at the house to see if it's on my 95 box). According to the MSDN Library (Jan., 1999), it's "Windows-16 Tool Helper library". Doing a Quick View on it shows that it's a 16 bit library, but the expected Windows version is 4.00 (32 bit Win and above). From what I'm able to gather from the MSDN, its purpose is to allow 16 bit apps to gain some of the functionality that 32 bit apps have. I could be mistaken in that impression, but that's what I got out of reading some of the associated articles.

Anyway, the bottom line is that it's dubious that VFP 6.0 is accessing it. The printer driver might be your best bet under the circumstances.