1 Date Range with multiple reports / queries

[andysgirl8800]

Thank you Brian. I am also at a loss. I may have to abandon this one. It's really bothering me that the queries work fine as a stand-alone...they recognise the dates in the date form and calculate properly. It's when those queries are used as the data sources for subforms that it loses focus on the date fields. Upon further experimentation, if I manually enter one date for the Text49 field, it then asks for the Text51 field. Access is wonky in this case. I even tore down my parent form AND date form (after backing up, of course) and rebuilt it from scratch. Same problem. *sigh* I just don't get it. Thank you again for all of your suggestions and assistance.

 

[andysgirl8800]

Rebuilt the entire thing from scratch...16 new queries, a new date form (with properly named Start Date and End Date fields), a new parent form, 8 new subforms....and......IT'S WORKING!

P.S. I've backed up the working "system" with 3 copies! *LOL*

 

[Brianwarnock]

Well done, and thanks for coming back on that. I searched the forum on subforms to see if I was missing something, I believe I mentioned on one of the other threads that they weren't a strong point.

Anyway cheers, I feel relieved.

Brian

 

[RichMorrison]

passing parameters to queries

I am coming in to this thread a little late, but what the heck.

Using 'Property' procedures to pass criteria to queries is fairly simple, reliable, and flexible.

Briefly;
1) Create a module called 'properties'.
2) Make let and get procedures.
3) In your form, call the let procedure after the user enters/selects a criteria. Any control on a form has an 'AfterUpdate' event that can call the let.
4) In your queries, put the get procedure in the Criteria cell.

This way you don't ever have to refer to control names or form names, just to procedure names. A query can be used from two or more forms this way.

This is a really brief description. I suggest you search the forum or Access Help for 'property procedure'.

Good Luck,
RichM