In VBA Access receiving a feedback from the printer that report page # is printed out

[Parwar Khoshnaw]

I have huge number of ID card to be print, each page contain 5 ID cards. when i sent report to print,due to some reasons i.e "Electric shutdown". all Pages will not be print.

I need a feed back from printer page by page , it mean i can resume the printing from the point where the printer have been stopped.

For that reasons , in need VBA command indicating the last page have been actually printed out.

before 2000 i were used Foxpro, i remember their was a command indicating the number of last pages are actually printed out

[zmbd]

PK:
AFIK: Access does not have a built-in function to retrieve printer errors nor any bi-directional communication with the printer.

If you remember the FoxPro command you used perhaps one of us knows if there is an equivalent in Access.

We also need to know the version of Office/Access and the operating system you are using.

[Parwar Khoshnaw]

@zmbd
Thanks zmbd for your prompt reply.

In this Project m using Ms Access 2010, windows 7

In the FoxPro, i remember their was a table contains feed back from printer, may you are a wear that their are command called eject in order to rich to row number 63 in continuous paper and start new page, so that table contain exactly how many times physically ejected , that mean number of eject is the number of pages are printed. but how was the function , since that was in 1996-1998 i don't remember

Thanks again, can above brief attend to any solution?

[zmbd]

old school days where every program basically used their own printer drivers.

that is not however (TBMK) what happens in more recent versions of window os nor with Access... the report is sent to the buffer or the print-spooler without any feedback from the printer; thus, we can tall how many pages were sent to the spooler but not how many were actually printed by the device...

the only other option I see here is if there is some sort of API call one could make to instance the printer directly and feed the report that way; however, that is well outside of my knowledge base.

In this case, I do not believe that there will be a solution to your problem using this method.

You could however create a query and/or code that allows you to take information from the last printed page "in-hand" (ie badge_id) and start your batch from that point. This would require the user to actually go to the printer, retrieve the documents, and read the information :-)