Update: I'm back to the drawing board now. Redesigned it to create records in batches of 50 and send that job before making the next 50. Each batch was done and sent as a job in sequence example: loop from 500 to 1, inner loop that prints after each 50 records generated. And the result is that the spooler printed jobs out of order after the 1st batch. It printed 500 to 451 properly, but then skipped then next 50 and went to printing 399 to 348.
In a second test, I paused the 2nd batch with a msg box until the first was done, and when printing resumed, it skipped the first 30 numbers after 451 and started printing at #420, 419 etc.... This also made me realize, that doing it in batches can allow for other print jobs to be inserted from other users. Can't have this happening either.