SubReport on Form

That's precisely why I placed the date in the same row as the event description.
The CF 'hides' the repeated dates but they still exist.
Placing them in their own row above will result in blank rows. So don't do it!
I also made the subform wider and moved the time section further to the right to fix layout issues.
You've also moved it into the same line as the date which isn't helpful

Design view:
1629153906773.png

The two fields on the right with yellow text are hidden fields: RankByDay & ReminderID
 
Last edited:
Ok thanks.
I'll open the original.

Thanks for all the help it is appreciated,
James
 
Adapt it as you wish but I doubt you can get the layout any better than I did
If you like the end result, please click the Like button. Thanks
 
Adapt it as you wish but I doubt you can get the layout any better than I did
If you like the end result, please click the Like button. Thanks
Been using the new Weekly Agenda for a few days now and I just
wanted to reiterate how happy I am with the results of your assistance.
Looks like it took a lot of time and effort for you to get this to work the way I would like.

Thanks again,
James
 
That will likely be as the date control is still there?
Remember, all Colin did was make the colour the same, so it was pretty much invisible, not remove it?
 
Seems like alot of code for just setting the forecolor so they are invisible.
 
The subquery I used in post #19 was the most important part of the solution as it allowed grouping by date. It may be worth studying that in detail.
Once that was used, a mixture of conditional formatting and hiding certain controls was used to layout the subform approximately as you had in your original subreport
 
I was only responding to the CF for setting the fore colour.
 
I'll give this a try and hopefully this will work for me. Thanks for keeping us posted. Will give updates too!
 
Hi Paul
I was responding to the OP's comments in post #28
Hi Colin,
I realise that, but OP just commented on 'a lot of code for just setting the forecolor so they are invisible. ', when all it was, was a simple CF statement.
Admittedly a fair bit of work to get some sort of order to enable CF to be used. Neat though. :)
FWIW I tweaked your DB to have them in time order per day as well, so any new entries occupied the (what is to me) the correct position.?

You know, sometimes I wish I was still using Access for some serious purpose, just for the mental stimulant. :)
 
Hi Colin,
I realise that, but OP just commented on 'a lot of code for just setting the forecolor so they are invisible. ', when all it was, was a simple CF statement.
Admittedly a fair bit of work to get some sort of order to enable CF to be used. Neat though. :)
FWIW I tweaked your DB to have them in time order per day as well, so any new entries occupied the (what is to me) the correct position.?

You know, sometimes I wish I was still using Access for some serious purpose, just for the mental stimulant. :)
Good idea to sort by time as well as date....

I do still enjoy the mental stimulus of finding solutions to problems e.g. using a subquery in this case.
The advantage to me is that I can then sometimes adapt solutions for use in my own applications
 
Sounds good.
Haven't done much in Conditional Formatting.
But this all works the way I want.
 
Conditional formatting works best for me in identifying financial errors in my report. It quickly highlight cells that contain values greater or lesser than a specified value.
 

Users who are viewing this thread

Back
Top Bottom