This is going to knock what's left of the "shine" off my "UniVerse Expert" crown, but I did not realize this could be done!
Thanks!! Don Kibbey Financial Systems Manager Finnegan, Henderson, Farabow, Garrett & Dunner LLP >>> [EMAIL PROTECTED] 03/23/04 01:52PM >>> From: "Cyndi Calvin" <[EMAIL PROTECTED]> (responding to Jeff) > LPTR!!! Thanks. That was what was missing. Works like a charm. > THANK YOU Now for lesson two in SETPTR. The first parameter is a "printer unit" which defaults to zero. So, a not uncommon thing to do is to issue multiple setptr commands, then direct output to them appropriately. One example might be: SETPTR 0,132,20000,0,0,3,BANNER MYFILE,BRIEF SETPTR 1,132,20000,0,0,3,BANNER MYFILE.NARROW,BRIEF SETPTR 2,85,20000,0,0,3,BANNER MYFILE.VERY.NARROW,BRIEF SELECT VOC SAMPLE 50 LIST VOC F1 F2 F3 F4 F5 LPTR SELECT VOC SAMPLE 50 LIST VOC F1 F2 F3 LPTR 1 SELECT VOC SAMPLE 50 LIST VOC F1 LPTR 2 Those are all MODE 3, which writes to the &HOLD& file. More appropriately, you might use the default MODE which spools, and use different AT's or DEST's within your SETPTR statements. I've seen people define their printer destinations using multiple SETPTR statements in their VOC LOGIN paragraphs.. That way they can simply LIST anyfile LPTR 1 and it'll show up on a particular printer, or LIST anyfile LPTR 2 and have it show up elsewhere. The same logic can be used within BASIC programs where you need to create multiple output files simultaneously. Perhaps for an AP run where you're printing checks and a register. In that case you'd specify the UNIT in the SETPTR, the PRINT and the CLOSE statements. Defaults for all are zero, but they're all specifiable. Rgds. -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
