Randy,

I had not seen that article but I will look into it. This sounds like it could be a possibility. Thanks

Bud


>Have you guys checked out KB article KBQ183522 which is on our support site (http://support.microsoft.com/support/).
>
>It discusses the floating point issues with the HP drivers and how you can workaround these problems by calling _FPRESET() after printing.
>
>Randy
>
>>Bud, et al;
>>
>>This one was a problem with a HP Laserjet5 printer driver. Note that the reports didn't have to be printed, but with that printer selected as the default and one of the getprinter() functions used, the system would hang...but only later, not right away. It was like the driver was slowly eating resources until the computer ran out of patience (divide by zero or infinite loop???).
>>
>>I have read of people having a similar problem in vfp5.0 (with laserjet6 drivers also). Funny it didn't show up for us until the switch to vfp6.
>>
>>The solution(so far so good) was to change to a laserjet4 driver. I wish that HP would resolve these driver problems ..i'm gonna start asking people what kind of printers they have before i price their work.
>>
>>Best o luck
>>Terry
>>
>>>Terry,
>>>
>>>Thanks. I am quite curious what you find. Unfortunately I can't go to each of my clients to fix this. They are scattered across the nation.
>>>
>>>>Bud,
>>>>
>>>>Unfortunately, I was unable to work at my clients last Thurs or Fri. as I had intended.
>>>>
>>>>I have a suspicion, from talking further to them, that this may be related to a HP5 printer driver problem.
>>>>
>>>>I am going back tommorrow, and will let you know what I find. Thanx for the interest.
>>>>
>>>>Terry
>>>>
>>>>>Terry,
>>>>>
>>>>>What is the status of your lockups? Have you had success in fixxing it? What and How did you fix it?
>>>>>
>>>>>TIA
>>>>>
>>>>>Bud
>>>>>
>>>>>
>>>>>