05-20-2016 12:27 PM
Running Prem ACT! 18.1 Update 2 on Win-10 PC.
Surprised no one reported it on board but I called support and confirmed they know about and working on fix.
Given in USA its May 5th 2016 [5/5/2016] pacific time zone and I want to find records I touched (changed) today.
Right click on Edit Date with Equal To (=) by "Today". My result is records with date of 4th.
Temp solution put in place of Today - 5/5/16.
Only problem with this is you can't create a group with query of Today you would have to edit the query every day.
I could not figure out a custom query workaround?
Seem like since 2011 Post similar issue:
When lookup "Birth Date within Next 0 Days" contacts with dates for 19th Feb appears.
When lookup "Birth Date within last 0 days" contacts with dates for 19th Feb appears.
When lookup "Birth Date within last 1 days" contacts with dates for 18th and 19th Feb appears.
02-15-2017 01:47 PM
I just confirmed D-04583 in V19 Update 4 that a Lookup on Edit Date by "Today" with times after 5PM is now working.
05-21-2016 01:04 AM
I think this might be because the dates are universal dates which are based on the UK Greenwich Mean Time (GMT) and not the actual local time.
05-26-2016 03:45 AM - edited 05-26-2016 03:45 AM
We haven't been able to replicate this issue in a EU or US install, however we're going to continue testing this over a couple of days.
I'll update again when I have more info.
05-27-2016 03:07 AM - edited 05-27-2016 03:12 AM
After retesting, we are still unable to replicate this issue. I suspect it's being caused by something particular about your environment.
I'll contact you via PM to arrange further troubleshooting.
05-27-2016 07:43 AM
I got your PM and will respond after this update of extra info to create the problem.
So this morning May 27th 6AM in Calf. (yes my clock and time zone Pacific is correct)
I updated my 1st record did lookup on Edit Date by TODAY and it showed up.
Then I changed time to 9PM changed a 2nd record did lookup only got the 1st record to show up.
Then I changed time to 6PM changed a 3rd record did lookup still got only 1st record.
Then I changed time back to 6AM changed a 4th record did lookup TODAY and now! I got Records 1st and 4th.
I could continue playing with my PC time but I think you can now figure out that the field also stores a time-stamp which Lookup is not following my Pacific time zone.
05-27-2016 08:39 AM
All SQL date and time fields include both a date and time component. If the time isn't specified for a date field then the time defaults to 12:00:00 AM (midnight). ACT! to allow time especially to be localized stores times as GMT with the local machine's time zone offset from GMT.
After going over your post again my guess is that you are using 12-hour indication for the system clock and the AM/PM setting is flipped. Check that.
05-27-2016 08:53 AM - edited 05-27-2016 08:54 AM
Windows 10 (Control Panel\Clock, Language, and Region)
Customize Format Time Tab in Time formats shows for both Short and Long the notion as lower case "h" (12 hr) If I change it to upper case "H" they say it would be 24hr.
I could change that to run more tests but I will not work in 24hr format so if that is it ACT! needs to address it.
05-27-2016 09:12 AM
I'm not familiar with Windows 10 but a logical analysis of the results of your test results indicated 12-hour system clock with AM and PM being reversed. I saw this problem several times when I was in ACT! tech sypport.