Yes, you are correct, they should work like that, it's just the apps I've worked on have all been one at a time. Don't waste time trying my suggestion.
Maybe, if you de-normalise your data to have one row with the data for the 2 labels? That is, instead of
row 1: label1
row 2: label2
row 3: label3
row 4: label4
you have:
row 1: label1, label2
row 2: label3, label4
just another WAG while I distract myself from some Flutter/Dart training I'm doing :)
Frank.
Frank Cazabon
On 01/06/2023 2:23 pm, Richard Kaye wrote:
Hi Frank,
I appreciate the response. I'll check on that but the 3 other formats I have working all run from the same process/cursor and print one label per page as expected until all rows are output.
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Frank Cazabon Sent: Thursday, June 1, 2023 2:11 PM To: profoxtech@leafe.com Subject: Re: Fun with label printers
Hey Richard,
If I remember correctly, these label printers only print one label at a time. Can you loop through your result set and print each label one at a time?
Frank.
Frank Cazabon
On 01/06/2023 1:21 pm, Richard Kaye wrote:
Hi ProFoxers! Let's start June off with an actual VFP question.
I've got the joy of generating labels using a DYMO 550 in my WWC web-based app. The precursor to getting this to work is standard MODIFY LABEL in dev, adjust the layout until everything preview/prints as desired, copy the label to my production environment. No special magic tricks or invoking the spirit of Cathy Poutney beyond saving the printer environment in the LBX. (Ah, the joys or proprietary hardware with proprietary paper sizes...)
Currently I support 4 DYMO label formats. Well, actually it appears to be 3 because the 4th one is giving me agita. The first 3 are all single label per page with varying dimensions. The problem child here is a tiny little 1" x 1" page with 2 labels per page. Previewing or printing the output in dev only generates a single page with the first 2 records regardless of how many detail records are in the cursor that runs the report.
While I continue to pound my head on this I toss it out to the collective wisdom...
TIA
--
rk
[excessive quoting removed by server]