Crystal,
I don't understand what's going on in this technique. I could just blindly copy (assuming it will work), but I like to know what I'm doing.
If this is simply a matter of converting it to bmp, I could do that directly to the image and store it that way. This is the only image we are using on the labels (other than the 2-D datamatrix).
Back to my original question, how does embedding, rather than linking, affect the speed at which a print job will spool?
Adam
--- In MS_Access_Professionals@yahoogroups.com, Crystal <strive4peace2008@...> wrote:
>
> Hi Adam,
>
> perhaps this will help:
>
> Print Failure on Reports with potentially 1000's of images, Stephan Lebans
> http://www.lebans.com/printfailures.htm
>
> what version of Access are you using?
>
> warm regards,
> Crystal
>
> (: have an awesome day :)
>
> --- On Wed, 7/20/11, AdamF wrote:
>
> > I'm printing bar code labels to a
> > label printer, WASP610. There's a logo on each label, in
> > addition to text and a 2D bar code image. The logo seems to
> > be gobbling up memory; it takes a while to spool the job to
> > the printer, and slows down the computer.
> >
> > A print job can be anywhere from 1 to 400 labels. Each
> > label is unique.
> >
> > The image originally was 350kb. With that, once I got up
> > above 50 or 60 labels in a print job, it would eat up 1gb of
> > memory and lock up the computer. The image didn't need to be
> > that size, so I shrunk it down to 15kb. This worked, sort
> > of. Large label runs work without eating up too much memory,
> > but the spooling still is slow, and the printer has to
> > repeatedly pause and start while waiting for the additional
> > data.
> >
> > The image is linked. What would happen if I embedded it in
> > the report? Would this speed up the print jobs?
> >
> > Adam
> > Denver, CO
> >
> >
> >
>
Tidak ada komentar:
Posting Komentar