>Marcus,
>
> You are right. I was debugging on site and found out that it was the hp 4000 drivers that were causing the problem. I would appreciate any extra info you could give me on the subject.
> I did install the dcom98.exe off of the VS6.0 cd. It did not seem to help.
>It was happening when an object was initializing. I was thinking of trying an older hp driver. I have the computers mapped to an old hp II printer and it is working fine.
> Thanks in advance. Jon Fritzler

Jon,
This problem is outlined in MS Knowledge Base article KBQ183522 at the Microsoft site. It is reported to be fixed in VFP6, but apparently they fixed the error message that came up and now you just get a lockup or bluescreen! The fixes suggested seem to work. There are three. 1. don't use HP drivers, use the MS drivers for HP printers instead. 2. disable the data numeric processor in the control panel under system/device manager. 3. reset the numeric processor using the _fpreset function. This seems to be the work around of choice. Here's how it goes:

** start code
DECLARE _fpreset IN msvcrt20.dll && only need to do once
=_fpreset() && insert this line after each of the commands below.
** end code

Use the =_fpreset() after any command that accesses the printer driver including the following:
GETPRINTER()
SYS(1037)
SET PRINTER TO
REPORT FORM

The article doesn't list the last two explicitly, but you need to use it if the HP is the default printer. The msvcrt20.dll is NOT distributed with VFP6, but its been on every machine so far. Good luck, and remember, you can test this without actually having an HP printer. The drivers from HP and viewing reports is enough to lock you up!
Marcus.