While processing 200 or so invoices into PDF format and saving to a file, the TERM SET_PRINTER message takes about 10 minutes to process. Is this normal?

I use a gif with a size of 17kb. The text is 2kb for each invoice.

Possible Richard. What happens if you do not use a PDF.

With 103 invoices, using the filename argument field 3 being 0 (no export), it took 1 second and produced a file size of 472kb.

With 103 invoices, using the filename argument field 3 being 1 (RTF), it took 1 second and produced a file size of 157kb.

With 103 invoices, using the filename argument field 3 being 2 (HTML), it took 1 second and produced a file size of 472kb.

With 103 invoices, using the filename argument field 3 being 6 (PDF), it took 37 seconds and produced a file size of 103kb.

With 103 invoices, using the filename argument field 3 being 9 (TXT), it took 33 seconds and produced a file size of 114kb.

__

With 277 invoices, using the filename argument field 3 being 0 (no export), it took 1 second and produced a file size of 1,269kb.

With 277 invoices, using the filename argument field 3 being 1 (RTF), it took 1 second and produced a file size of 413kb.

With 277 invoices, using the filename argument field 3 being 2 (HTML), it took 1 second and produced a file size of 1,269kb.

With 277 invoices, using the filename argument field 3 being 6 (PDF), it took 522 seconds and produced a file size of 234kb.

With 277 invoices, using the filename argument field 3 being 9 (TXT), it took 447 seconds and produced a file size of 302kb.

Just wondering if this is normal.

Richard, this looks like the ocx command that saves the print image to a printer file is what takes so long. The txt is doing this because there is a bug that is fixed on the next release. I will do some verifications to this but I suspect that it is just a function of the OCX.

View this thread on the Works forum...