06-08-2009 02:54 AM
I'm using ACT! by Sage Premium 2009 (11.0) Version 11.1.183.0 and I've done this query:
...and you can see although I'm only looking for anything where the date has "06" as the month, it is bringing up other records as well (they appear to be dates where the days are 01 of the next month).
Can you please confirm this is a bug and/or advise of a solution.
06-08-2009 08:03 AM
06-09-2009 03:35 AM
06-09-2009 06:10 AM
I am unable to reproduce in ACT! 2009 Premium 11.1. I'm using the same dates in the screenshot.
06-09-2009 08:09 AM
David
Check my other post to this thread. I was able to reproduce the problem. This is an ongoing problem with date fields in the ACT! program. All date fields have a time component in the SQL database and if it's a date field that does not use the time component, that time component is set to midnight. In addition the dates are time zone sensitive as an offset from Greenwich, accessing the date field for queries from a different time zone or influenced by daylight savings time, you can get these kind of one day date errors. My fix would be to set the default time to noon rather than midnight to at least minimize the problem. I have separately reported this as a bug on the ACC newsgroup.
06-09-2009 09:05 AM
I haven't been able to reproduce in house on any workstations or images. After speaking with another agent, we found an existing reported issue for the UK locale that will be resolved in a future version.
06-09-2009 09:09 AM
David
I'm sending you a private message