Dates are being reordered in report

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jaccess
    New Member
    • Apr 2007
    • 26

    Dates are being reordered in report

    Hello,

    I am running MS ACCESS 2003 and have run into a seemingly simple problem. Hopefully all I will need is a quick fix.

    I have a report based on a query that lists a date, items received, items processed, and items remaining. The query gets a date range from a form. I am trying to total the items received, items processed, and items remaining fields.

    When the report is run without anything like =Sum([fieldname]) in the footer, the dates are listed in ascending order ( which is what I want and how the query was set up)

    When the report is run with =Sum([Fieldname]) in the report footer the dates are listed in no particular order.

    Is there something simple I have missed? If any detailed info is needed please let me know.

    Thank you.
  • jaccess
    New Member
    • Apr 2007
    • 26

    #2
    Something I have noticed is that the report will list the dates correctly if the range is within the same month. For example if I enter my date like start date: 10/01/2007 end date: 10/20/2007 on my form the report appears correct. But If I enter start date: 10/01/2007 end date: 11/09/2007 the dates are mixed up.

    I will do more testing with my dates to try and see any patterns.

    Comment

    • jaccess
      New Member
      • Apr 2007
      • 26

      #3
      Well I may have fixed my problem.

      So just to recap: I have a query that produces the results I need ( Date sorted in ascending order with 3 other fields). The query gets the date range from a form.

      The report which is produced reorders my dates in no particular order if the date range spans over a month ( Oct 23 to Nov 5 for example.)


      A solution I found was to look at Sorting and Grouping (under the view menu) within the report and sort the data there.

      Now the dates are sorted in ascending order like they should have been to begin with. I do have a field named DATE, perhaps this may explain the anomaly as it is a reserved Access word apparently.

      If any Access pros out there think this solution will cause more problems or have a better fix please let me know.

      Thanks

      Comment

      Working...