Emmitt: >Do you do: > OUTPUT PRINTER > PRINT report > OUTPUT SCREEN >between each invoice, or do you: > OUTPUT PRINTER > PRINT report > PRINT report > PRINT report > OUTPUT SCREEN >If you do the former, you should end up with scads of entries in the W2k >print queue. If the latter, you'll have one entry in the queue. I'd >suggest the former.
I do the former. I have to because for each client that I am cursoring through, I am also doing calculations in the program and writing the results to one of 2 output files so there's alot of OUTPUTing going on! Ben: >I'd suggest the pausing routine as a trouble shooting method, if not >a solution. Have you watched the queue as the printing is going >on? Do the print jobs flush to the printer very quickly? I haven't been onsite yet to watch. I will do that the next time I'm there. That's what I want to do -- every 200 jobs or so to have a pause that says "press [ok] when the printer has caught up". If someone is there to press the button, the program works so fast that there would hardly be a pause. But I hear the whine "but we want it to be unattended...". Of course they do, but this is better than never getting a complete run. >If nothing has >changed other than the printer, maybe it's the printer that can't >handle all those separate jobs and more memory is a _liability_. That's what I can't figure out. WHY WHY WHY does a brand new laser screw up when pushing thousands of jobs to a slow, slow old HP Laserjet works perfectly. Javier: >You can define the page header to be a variable that >resets the page number with each customer and prints the tear-off coupon on >the first page and then switches to the customer name and address on >subsequent pages. I'm not getting this. I need the coupon as the 'report header' so to speak, only being at the top of the first page only, but then every page (including the first) needs stuff like addresses, column headers, etc. >Also, you can set up the application so it can run in the >background, so the computer can be used to do other things; How true that is! I'll mention that to her -- I can put in a pause after every statement and tell them to just minimize the app and forget about it. It just gets in her craw (?) because she spent money on a fast printer and the thing is going to wind up printing the same speed as a slow one. >One last thing, printer memory will make a huge difference, the more memory the >printer has, the faster it will receive data from the spooler and thus free >it up, I would have thought so, but again, a slow laserjet with practically no memory at all is getting all the jobs perfectly. Myron: >Below >is an address from a Microsoft support site regarding print spoolers. It >might be worth while to see if you can tweak Windows. Thanks, I'll check it out. Karen ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
