| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 1636.1 |  | BUSY::SLAB | Candy'O, I need you ... | Wed Mar 05 1997 12:21 | 8 | 
|  |     
    	Go into the report, click on "sorting and grouping", and add a
    	grouping for quarter with either a header or footer line.
    
    	If you're using DatePart to retrieve the quarter number for you,
    	it appears that Access will return a calendar quarter and not a
    	fiscal quarter [just in case it makes a difference].
    
 | 
| 1636.2 | Module1 table parameter input required? | 55028::VAART_R |  | Fri Apr 25 1997 15:12 | 21 | 
|  |     I've a problem with sub-reports which I hope I can make clear as
    follows:
    
    A table contains information of modules, being Books, Scenarios and
    Procedures. Each record is Identified by a code starting with B, S or
    P. To connect these tables I had to duplicate the module table in the
    Relations window. These resulted in a 'module', 'module_1' and a
    'module_2' table object.
    The same applies to queries i've build. Sofar it worked fine for me,
    however in one report I select a book and print scenarios as detail
    lines. As part of the detail lines I included a subreport. This report
    is Scenario - Procedure report. 
    To connect these reports i've set for master link: module.module_id and
    for child link: module_1.module_id.
    
    When running the report a window is poping up and requesting an entry
    for module1. Just pressing OK gives the report I want.
    
    How can I avoid the pop-up?
    
    Roderick.
 | 
| 1636.3 | Unused sorting order parameters? | NSIC01::KLERK | Thunderbirds are Go | Tue Apr 29 1997 09:21 | 8 | 
|  | 
  I recall that when a report is made and you specified some sorting order
  (not all of which you may now still use), a popup would come up. Removing
  the no longer needed sorting parameters also got rid of the popup.
  Would this apply to your report?
  Theo
  
 | 
| 1636.4 | It's a feature | OSEC::pervy.mco.dec.com::GILBERT | Oh. | Tue Apr 29 1997 14:57 | 5 | 
|  | Essentially Access is saying it wants you to specify the value of an item that 
isn't defined explicitly. A typical mistake is to mis-spell the name of a field 
used in a query. Access thinks you want to specify it at run-time.
 
 | 
| 1636.5 | possibly this | XSTACY::PATTISON | A rolling stone gets the worm | Wed Apr 30 1997 12:36 | 12 | 
|  | 
I had a problem like this recently, where I had a field called 
tblMachine.ID in the LinkChildFields. A popup kept coming up asking
me for a value.
I changed the underlying query to return an alias, such as 
	tblMachine.ID AS MachineID
and then used MachineID to link the subreport. Problem went away.
I never bothered to find out why, but thought I'd mention it.
Dave
 | 
| 1636.6 | Alias: it!works!fine![Now] | 55028::VAART_R |  | Wed May 07 1997 13:08 | 6 | 
|  |     Re -.3,4,5
    
    I managed to solve the problem using the answer in .5.
    Thanks.
    
    Roderick.
 |