>>> on a report. a PrintPageNo or PrintWhen prop will dynamical define
>>> which page to print (and a "print tab boarders" prop that defaults to
>>> false.) That way an address block (name/addr1/addr2/city,st,zip) can
>>> have several formats for
>>> the last line to cover other countries.
>>
>>
>>
>> Yeah, I like that idea a lot.
>
>
> I've anticipated the desire to have an unlimited number of detail bands
> and groupings, to lay them out separately, and to conditionally print
> one or more detail bands. The designer interface to each of these
> elements could indeed be a pageframe. A "page" on a report doesn't
> necessarily have a 1:1 correlation with a "band" (but it could). Am I
> understanding the vision correctly?
>
Maybe - but your description of bands and groupings isn't too clear.
I'll beef up my exaple:
create table Addr (
cName varchar(60),
cStreetNo varchar(10),
cStreetName varchar(60),
cBlock c(10);
cAddress2 varchar(60),
cCity varchar(30),
cDirstrict varchar(40),
cPostCode varchar(20),
cCountry varchar(20),
nLayout int )
nLayout defines which arangement to use.
1:
cNamecStreetNo cStreetName
cAddress2
cCity, cDirstrict cPostCode
2:
cName
cStreetNo cStreetName
cAddress2
cPostCode
3:
cPostCode
cCity
cDirstict - cBlock - cStreetNo -
cAddress2
cName
1 is for US, 2 is for Sweden, 3 for Japan (well, don't use me as a source - best I
could come up with after reading
http://en.wikipedia.org/wiki/Japanese_addressing_system )
In VFP you would have all of those text objects (is there a name for them?) layed
out in a big pile, and then set the .PrintWhen to "nLayout=1" for some and 2 for
others etc so that the proper set prints.
My idea is to use a pageframe so that
A) it is easier to see in the designer,
B) you don't have to set the .PrintWhen more than once
C) you could use the same class for doing the data entry. (I just thought of C)
^C
©2005 Carl Karsten |
