2 Replies Latest reply: Sep 7, 2012 2:54 AM by Mark Perry RSS

    Master date controls that link in with other controls

      I get the impression from posting on this forum that it's legitimate to have several different date selectors. For example if I had some sort of eCommerce database that had seperate order and shipping dates for goods then I guess it's kinda obvious that I would want to treat these as seperate entities and allow the user of my report to decide which data to use for their analysis.


      The report I'm working on uses date information from three different applications. One of the applications has two distinct dates - the date a call was resolved, and the date that someone spent time working on a call. I also have dates from a timesheet application (i.e. when someone was at work) and dates from a project management system (how much time someone spent on a project on any given day).


      So I have created a report, and now have four seperate sets of date pickers like this:




      This is quite unwieldy - I have to say to users 'select the date you want to look at 4 times', and they say to me... well, you can imagine.


      I tried adding a field called 'link_month' to a couple of the tables that the dates come from, and then adding a new table to my database with a single column called 'link_month' and just adding January, February... etc. to it to see if I could create one master month field in QV that all the other month fields would link to. But (as I suspected) when I loaded it all back in QV complained about loops in the data structure.


      Please could someone advise how to create a set of master date controls that link to the others and don't screw up the data structure? Thanks.