David Emerson
newsgrps at dalyn.co.nz
Sat Jul 3 02:36:36 CDT 2010
Rocky, I think your original idea would work - Collating the assembly part numbers as part of a where clause in the main reports query and use the report groups to include the sub reports for each assembly part? Regards David At 3/07/2010, Ramz . wrote: >How about looking into the possibility of treating such report as a >custom-label report? If the most you'd get per page is half a page of >print-out, then probably you can design a custom two "label" report. HTH > >On Fri, Jul 2, 2010 at 8:44 PM, Rocky Smolin <rockysmolin at bchacc.com> wrote: > > > Well, it's really one report run many times for different parts. Think of > > it > > as a bill of materials report. I pass the assembly part number to the > > report and it runs. As each work orders are opened automatically, the Kit > > List for the work order is printed. So it's really just one report run > > many > > times for different assemblies. That's where I'm a bit stumped. If it was > > a > > bunch of different reports, I could make each one a sub report. But it's > > the same report. > > > > R > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart > > McLachlan > > Sent: Friday, July 02, 2010 5:35 PM > > To: Access Developers discussion and problem solving > > Subject: Re: [AccessD] Bunch of reports with no page break > > > > That's exactly the way I do it - embed them as sub-reports in a "wrapper" > > report. > > > > -- > > Stuart > > > > On 30 Jun 2010 at 22:32, Rocky Smolin wrote: > > > > > Dear List: > > > > > > I added a feature to my app to automatically release a bunch of work > > orders. > > > Client loved it. > > > > > > Then the client wanted to have the Kit List printed for each work > > > order released - no problem, client loved it. > > > > > > Now since many of these reports take only 1/3 to 1/2 page, the client > > > requests that they be printed without the page break - save a tree. > > > But I'm not sure how to accomplish this. I suppose I could make the > > > Kit List report a subreport in the detail section of a report, the > > > record source of which would be the list or work orders to print the > > > kit lists for, but I'm not sure that would work. Any ideas? > > > > > > > > > > > > MTIA, > > > > > > Rocky Smolin > > > > > > Beach Access Software > > > > > > 858-259-4334 > > > > > > www.e-z-mrp.com <http://www.e-z-mrp.com/> > > > > > > www.bchacc.com <http://www.bchacc.com/> > > > > > > > > > > > > > > > > > > > > > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com