Hey Guys,
sorry, funny thing but I have to announce it. One of my customers does reports up to 31.12.2173. Up to 30.09.2173 everything looks okay:
When I change to 14.10.2173 the Datefilter-function looks like that:
At my example no database is in behind, I only used the NP-function "Date Filter". Jet Version is 19.6.19018.1, Excel 2016, Windows 8.1
Is it a feature or is it a bug? :D
Thanks!
KR, Marit
well Marit, since one of my co-workers was recently updated to the latest version of Jet, and I'm still running 2018 version (specifically 18.1.18149.1). I thought I'd test your dates
On his computer - it returns the error you are showing, but my version of Jet (the older version) works just fine.
So, I'm guessing you've found a bug in the newer release.
Hello Mait -
As you may know, Excel represents dates as simple numbers. 12345, 67890, etc.
There are then translated into whatever date format the user specifies.
In the case of October 13, 2173... that number is 99999
As you can guess, the next day is 100000.
As it turns out, the internal code in Excel that Jet calls upon to translate that into a date returns... yep... 100000
Instead of using 01.01.1950..31.12.2173, I would recommend one of the following filters:
*
01.01.1950..
Hey Harry,
hard to tell the customer, the thing working at a former version is not available at the current version of Jet Reports. I told him to use the filter until 13.10.2173 up to Jet will provide any solution for this in one of the next hotfixes or versions. Don't ask me, why he's reporting so far into the future but he does and it's my job to support him on this.
;)
Hello Marit -
What I suspect is behind the difference between now and the prior version is that the Jet add-in is now based on Excel's XLL format (older versions were based on the XLAM format). Different formats would require that different internal Excel code be used.
