Date Range Class / Component added to ESBDevLib

Work has been progressing well with the Class and Component for Date Range Calculations for ESBDevLib for VCL/FMX. Like with the other Class/Component pairs in the Calendar Engine, we are supplying both ways to access the Library of calculations involved. Similar to ESBPCS for VCL, most calculations are also available as standalone procedures / functions – thus giving you the flexibility to program the way you wish – or at least that is what we are aiming for 🙂

Here is a screen shot of the Demo for the Date Range Class:

Date Range Class Demo

And here is the Component version in the IDE Object Inspector:

Date Range Component

Now to finish off the Date/Time Range Class / Component 🙂

About esbglenn

Software Developer working at our Family owned business, ESB Consultancy, which is located in Kalgoorlie-Boulder, in the Eastern Goldfields of Western Australia.
This entry was posted in Beta Development, Calendar Engine and tagged , , . Bookmark the permalink.

4 Responses to Date Range Class / Component added to ESBDevLib

  1. Glenn et al,

    I think the Date Range component is great. Waaaaay back when, I made a compound component and it’s been a large success for my users. You graciously have had me in your user base for a long time just for making this suggestion to you all those years ago.

    I do have a couple of new suggestions to make. My date ranger built from ESPPCSvcl parts, has a few more ranges available as an immediately defined start and finish date. I allow for the Current, Previous or Next … Day, Week, Month, Quarter, Year. My immediate drop-down ranges also include Month to Date, Last 13 Weeks, Year to Date and Last 365 days. Finally, I include Next Business Day, Prior Business Day and the Ultimate, Unlimited Date Range. I haven’t had a request for a different range in years. But other users may vary. i would be intrigued to learn of another date range requirement.

    I have a drop-down menu in between the dates to provide this menu list of ranges. Works the same for either left or right click. I used to use a simple bitBtn for the menu, with a downward pointing triangle. But I decided a couple of years back to make it a simple button that had the words PICK RANGE on it. Cleared up a large part of the learning curve for new users. And I even changed the colour to red or green depending on whether it was a an actual range with a lesser starting date. The latest change further includes a label on the RIGHT side of the two dates that shows the word version of the date range, or “Manual Date Range” if there has been no use of the drop down menu to pick a range. Having the word version of the range is handy when doing reports (Goes into Title, while the date range is indicated in the footer for those who prefer seeing it there).

    Obviously, what I have done is easy. All but one of my users is in English Canada. Doing it for the lone Quebecois client took some work, but it was well-compensated work. Doing all that I have done would require a fair number of translations, which will slow down this component’s development. Thus, I will still use my home-rolled version into the currently foreseeable future. But having a professionally coded version with all the error checking (no need in all likelihood for the colour indicator on the menu button) will be something I will watch carefully. At some point, you will make me mothball my effort.

    I’m looking forward to that day. Thanks. GM

    NOTE: Oh, and the one range you MIGHT want to consider is adding Financial Year.

    • esbglenn says:

      Gary,

      Many thanks for this detailed post – very useful to hear how you use and what you require in the area of date ranges. Some ideas for us to look at for the next release of our Date Calculator (do you have that – if not post me an email and I’ll supply you a copy). I’ve added your post to the ESBPCS “to do” list so we can see what we can add into ESBPCS for VCL as well as into ESBDevLib. 🙂

    • esbglenn says:

      Gary – Financial Years are bit trickier – many years ago in a project I added the selection of Financial Year – being 1 July to 30 June – as that was our Financial Year. Then I found that was not the case in all countries. I then also found that companies / businesses are often constructed around different Financial Years. So some thought will be needed in the “naming” of such ranges 😉

  2. Glenn – Re the Financial Year, it would have to be customizable with a property. My biggest client just got done with their FYE last Monday. Fun time for all. Assuming all is the total population of Micronesia Mountain Sherpas.

    By the way, I failed to note that the whole component I use is done with ESBdates and a couple of standard date components. I switched them to ESB versions when your library first came out. Thanks again. GM

Leave a Reply