Hi,
I have a program that's bee written with Access. In that application, there
is a form that let you print a sequential batch of sticker, you just need to
specify from what number to what number to print.
The problem is that once the "Print" button has been pressed, the
access-application freezes until the entire data is processed and printed.
How could we avoid this? Is this because access can only manage one job at
a time (in that cas, when the application is sending data to the printer, it
cannot do anything else)?

Thanks,
Etienne

Etienne,

Wild guess, but any chance you have "Print directly to the
rpinter" checked on the Advanced tab of your rpinter
properties? This prevents Windows from using the print
spooler, and makes them wait for the rpinter to actually
print the job.
If that's the case, try to remove it and see what happens.

HTH,
Nikos
>-----Original Message-----
>Hi,
>I have a program that's bee written with Access. In that
application, there
>is a form that let you print a sequential batch of
sticker, you just need to
>specify from what number to what number to print.
>The problem is that once the "Print" button has been
pressed, the
>access-application freezes until the entire data is
processed and printed.
>How could we avoid this? Is this because access can only
manage one job at
>a time (in that cas, when the application is sending data
to the printer, it
>cannot do anything else)?
>
>Thanks,
>Etienne
>
>
>.
>