FYI,

I found the problem on our end. Our situation was similar. No ActiveX components, and the only time the user gets an error is when trying to print. We also have a BMP logo file that had previously been stored into a general memo field in a preference table.

The user did not have the bmp file on their local hard drive or any network drive mappings. The problem was resolved once they copied the bmp to a shared drive, and restoring the bmp into the general memo field.

There is one other item that was changed that may have made a difference. Previously the bmp file name was 18 characters long. I had them rename to a shorter filename (4 char). Don't know if this had any bearing, but it works now.