Avery 2163 Mini labels

procogo

Hello:

I am trying to create a report to print on the Avery 2163 mini mailing labels. The problem is that this label is 1 column. The top half of the sheet has 2 labels, each 2" x 4"... same for the bottom... BUT, they are separated by a 1" gap. Printing to the top 2 labels is a piece of cake, but how to you force the band to drop down an inch so that it can print the bottom 2?

Here is what these labels look like. http://www.avery.com/avery/en_us/Templates...0002118140aRCRD

Starting from the top.
- 0.5" top margin
- 2" high (label #1)
- 2" high (label #2)
- 1" gap
- 2" high (label #3)
- 2" high (label #4)
- 0.5" bottom margin.

Many thanks,

Dale

procogo

Ahhhh Use OnManualBuild. Very very cool. Anyone know what the units are for CurY? I need to drop it down 1 " (I know, should be easy to find but I haven't found it yet).


procedure Page1OnManualBuild(Sender: TfrxComponent);
begin
Engine.ShowBand(MasterData1);
Engine.ShowBand(MasterData1);

Engine.CurY := Engine.CurY + 20;

Engine.ShowBand(MasterData1);
Engine.ShowBand(MasterData1);
end;

procogo wrote: »

Hello:

I am trying to create a report to print on the Avery 2163 mini mailing labels. The problem is that this label is 1 column. The top half of the sheet has 2 labels, each 2" x 4"... same for the bottom... BUT, they are separated by a 1" gap. Printing to the top 2 labels is a piece of cake, but how to you force the band to drop down an inch so that it can print the bottom 2?

Here is what these labels look like. http://www.avery.com/avery/en_us/Templates...0002118140aRCRD

Starting from the top.
- 0.5" top margin
- 2" high (label #1)
- 2" high (label #2)
- 1" gap
- 2" high (label #3)
- 2" high (label #4)
- 0.5" bottom margin.

Many thanks,

Dale

gordk

engine is always working in pixels.

procogo

Actually, this *almost* works, but it prints the same address on each label.

How do I make it put a different record on each label?

procogo wrote: »

Ahhhh Use OnManualBuild. Very very cool. Anyone know what the units are for CurY? I need to drop it down 1 " (I know, should be easy to find but I haven't found it yet).


procedure Page1OnManualBuild(Sender: TfrxComponent);
begin
Engine.ShowBand(MasterData1);
Engine.ShowBand(MasterData1);

Engine.CurY := Engine.CurY + 20;

Engine.ShowBand(MasterData1);
Engine.ShowBand(MasterData1);
end;

gordk

connect your mdband dataset. prop. don't need on manual build event.
set you cury in the oap or obp event of the band.

or in the band oap move the dataset to next record if you want to use masterdata not connected to a dataset

set the band height = the label height.
in the obp event of the band write code
if <line#> mod3 = 0 then engine.cury := engine.cury + value

what constitutes one record a pair of labels or 1 single label.?
note that you can set a databand to a set number, rowcount prop, don't connect to a dataset
control movement from code

procogo

I'm almost there. If I call MasterData1.DataSet.Next right after showing the first MasterData band, it works. But if I add any more calls too MasterData1.DataSet.Next, it just stays on the first record?

Regards,
Dale


procedure Page1OnManualBuild(Sender: TfrxComponent);
begin

Engine.ShowBand(MasterData1);
MasterData1.DataSet.Next; { <--- this works as long as the others below are commented out}

Engine.ShowBand(MasterData1);
//MasterData1.DataSet.Next; { <--- uncomment this and it just sits on the first row of the dataset}

Engine.CurY := Engine.CurY + 20; {gap}

Engine.ShowBand(MasterData1);
//MasterData1.DataSet.Next;

Engine.ShowBand(MasterData1);
//MasterData1.DataSet.Next;
end;

procogo wrote: »

Actually, this *almost* works, but it prints the same address on each label.

How do I make it put a different record on each label?

gordk

don't use omb event, connect the masterdatabands dataset prop to the correct datasource.
write code in the obp event of the band to check where you are (which line, system variable Line# or line which ever is approp ) and if on the 3 set the engines cury

procogo

Thanks so much for the help Gord!

That did it.

Dale

gordk wrote: »

don't use omb event, connect the masterdatabands dataset prop to the correct datasource.
write code in the obp event of the band to check where you are (which line, system variable Line# or line which ever is approp ) and if on the 3 set the engines cury