what have people done for ssrs params needing very precise start and end times

  • Hi we run 2019 standard.  one of our mfg locations requires somewhat precise start and end param times along with the start and end dates controlling how an ssrs report is filtered.

    our main user doesnt like the idea of them typing hh.mm.ss.nnn next to the date showing when they pick a date from the calendar icon.  so we are talking about separate text boxes for the two times.   i can even see drop downs for hrs, drop down for minutes, drop downs for seconds and talking him out of what i think are microseconds, the nnn part.

    does the community have any ideas?   that sounds like a lot of drop downs.

    • This topic was modified 3 months, 1 week ago by  stan. Reason: spelling
  • i think we'll start like this...

    Start Date ____  X      and Time: ____             End Date ____   X        and Time:______

    X represents the ssrs calendar param icon.  The horizontal bars represent param boxes.   In the time box they'll type HH:MM:SS.   We'll forego microseconds.   If (cant remember) the calendar icon generates a time next to the date, we'll tell them it will be ignored or maybe we'll generate the same default times in the time text boxes.  the query will parse the times entered and we'll tell them of some sort of default behavior or error message if a time is invalid.

    • This reply was modified 3 months ago by  stan.
    • This reply was modified 3 months ago by  stan.
    • This reply was modified 3 months ago by  stan.
  • stan wrote:

    Hi we run 2019 standard.  one of our mfg locations requires somewhat precise start and end param times along with the start and end dates controlling how an ssrs report is filtered.

    our main user doesnt like the idea of them typing hh.mm.ss.nnn next to the date showing when they pick a date from the calendar icon.  so we are talking about separate text boxes for the two times.   i can even see drop downs for hrs, drop down for minutes, drop downs for seconds and talking him out of what i think are microseconds, the nnn part.

    does the community have any ideas?   that sounds like a lot of drop downs.

    The user said they don't want people to be typing the dates and times so the only alternative appears to be one on-screen field for each temporal part.  I don't know SSRS but go for the gold and allow for either typing directly in the field or allow the use of the pull-down associated with the field.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply