Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help Detail section fixed rows!!

Status
Not open for further replies.

crustas

IS-IT--Management
Feb 10, 2002
6
GR
Hello

I have a problem in seting the max number of rows in the detail section. I have at the most 16 components for each product id , but i want to split in to groups of 8 (for labeling purposes). I've have tried several aproaches to this problems and nothing it keeps the same, show allways the 16 rows. I would like that someone could bring me some light to the problem.

What i have
LABEL NUMBER 1
product id (product header)
xxxxxxxxx
components (detail section)
1 xxxxxx
2 xxxxxx
...
16 xxxxxx (the max number of components)

what i want
LABEL NUMBER 1
product id (product header)
xxxxxxxxx
components (detail section)
1 xxxxxx
2 xxxxxx
...
8 xxxxxx

LABEL NUMBER 2
product id (product header)
xxxxxxxxx
components (detail section)
1 xxxxxx
2 xxxxxx
...
8 xxxxxx


Thanks in advance
Crustas
 
If you have access to a component_id (ie 1-16), create a dummy group column in the recordset, eg

group_id = Fix((component_id - 1)/ 8)

You can now create a section in your report to break on this group. Good Luck,
Mike T
 
Thanks for your reply

i have thought in that option, but what happens in the real is a litle more complex than i initialy explain.

The number of rows is undeterminated for a product_id, it is always changing depending on the product updates. And thereis thousands of product_id.

A certain product_id may generate one, two, three or more labels with 8 rows it depends on how many components has in the "instant moment".

With your alternative i would have to do a extra heavy SQL update/query (inserting component_id number sequence for each product_id) each time there is an update wich would be very time consuming and adding another field would have
impact in the database size.
Thanks again,
Crustas

Any other sugestion?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top