Bug: Julian dates do not work in queries

Post by **Anonymous** » 03 Dec 2009 15:54

Julian dates do not behave correctly in queries e.g. if specifying that a field should be included/excluded if it is earlier/later than a date/parameter the Julian dates all come out regardless of the filter being imposed.

ID:4193

Post by **SimonOrde** » 04 Dec 2009 10:10

In the current version, date matching in queries only works if the dates are specified in the same calendar. If you switch to specifying a date using the Julian calendar, you should find that Julian dates will be matched correctly, but Gregorian dates won't. However, Family Historian should be able to do better than this, and we have made a note accordingly. Thank you for pointing this issue out.

Post by **Anonymous** » 04 Dec 2009 11:17

Many thanks Simon [smile] the reason I needed it was to span centuries in queries.

Family Historian User Group