Same here. I had to print parts of invoices from different trays (some preprinted and some plain). I did not seem like it should be as difficult as it turned out to be. I got that to work in Crystal, but had to make a VB dll to handle the events. Now I have a question about licensing for Crystal (it is pretty pricey for a web app if you want to get your data from VFP and pass it to the report via ado and you have more than 5 concurrent customers) I am moving all the web reports to xml with an xslt sheet I wrote, now that I found the handy dandy page break function in DHTML and how to display stuff in the browser, but not print it.

>That's understandable, depending on the ability of the users. It's certainly easier for most to remember to print invoices to a printer named 'Accounting' than to remember that it's the "HP LaserJet Super-Duper on Server BigServer" However, in a Citrix environment, it would be consistent for all users. I took an extreme apparoach - I started using Crystal Reports, mainly because the 4 important reports in my latest app couldn't possibly be done with the VFP report writer, at least not look like the client requirements stated, and it conveniently works around any issues of storing printer information.
> I remember seeing someone (probably Ed Rauh, he's the Windows API expert) post some code to call the windows API functions to select the proper printer. Something like that might solve your problem by forcing the proper printer in code.
>
> Randy
>
>>Ok, it was just a guess.
>>I just remember, some years ago, that I had a situation where some of the workstations in the building had the same printer mapped with a different name than my computer did, and it caused this to happen. I think I might have renamed the printers on my computer to make them easier to distinguish. Of course, this was VFP3 and Win95.
>>
>>
>>Bill