Hi Jim,

Thanks for your input on this...just more info that makes it easier to deal with the culprit (probably HP). Will post a message back here if I do (or do not) make any progress so that if someone searches for same issue in the future, they can see if there is any resolution. Thanks. Also thanks for the suggestion on Crystal (use it now in another app somewhat).

Albert

>Albert,
>
>Yes we have gone round and round with both MSFT and HP on this issue. We have gotten everything from update the driver, to call HP, to "do you really now what your code is doing" kind of answers. I always worry about the "do you really..." type responses. People in glass houses should never throw stones....
>
>The best solution I have found if it is not the TAG, TAG2 issue is what you are doing now. Dumb down the print driver or shut off the advanced HP print features and basically make it a one way feed. I wonder if the solution is to setup a buffer to print (DBF, ADO Cursor, etc and then Crystal or Word to then print the report? VFP's report writer and engine has not improved much in years and these problems may be MSFT's way of finally breaking us of our habit.
>
>We built an interface to Crystal (Great Support! and well documented) and besides the rare OLE nightmare error (usuallly caused by configuration problems) this has worked great. Crystal's runtime is free and Hentzenwerke Books has a great guide to building the interface.
>
>Regards and keep me informed if you can,
>
>Jim Smith