Recent content by DFlynn24

  1. D

    Repeated Values in One-to-Many Query

    Plog, disregard that last post I was able to figure out what you meant.
  2. D

    Repeated Values in One-to-Many Query

    Sorry, I'm not sure I 100% follow. What do you mean by bringing down the date and unchecking it? Because I would like the date to be visible in the query result.
  3. D

    Repeated Values in One-to-Many Query

    Plog your query worked like a charm, thank you very much. Just one question: one field I included in the second query's SELECT clause was the incident date. However, when I run the query and am in the datasheet I do not have the ability to apply a date filter because Access isn't recognizing...
  4. D

    Repeated Values in One-to-Many Query

    I'll have to give that a try. Thank you for taking the time out to write that out.
  5. D

    Repeated Values in One-to-Many Query

    MajP, but I do need the child records... I, and our partners, want to see which victims had which type of packaging in what places. Many of the incidents have multiple types of packaging. I want to be able to pull a month's worth of this data and easily be able to export it and e-mail it to...
  6. D

    Repeated Values in One-to-Many Query

    theDBguy, I do appreciate your input! Plod, no problem see the attached spreadsheet. If you need further clarification just let me know.
  7. D

    Repeated Values in One-to-Many Query

    Well if I want to Pivot Table the data and see how many incidents a certain town had, it would inflate the numbers. If one incident had seven different kinds of packaging present it would count the town seven times when it should only be counted once
  8. D

    Repeated Values in One-to-Many Query

    I would keep my CaseID field so I don't think it would get completely lost. The repeating of names, dates, etc. is the real problem because it throws off analysis that gets conducted down the line
  9. D

    Repeated Values in One-to-Many Query

    I am using the datasheet view. I would like to try to avoid using a report for two reasons: one, often times we will apply filters to see incidents over an extended period of time (by month, for example) by county, township, etc. Second, is that we often export the data to Excel and reports I...
  10. D

    Repeated Values in One-to-Many Query

    Good Morning, I'm in the process of reformatting a database at work, which contains drug-related incidents. There are two tables; incident/victim information and packaging color. The goal of my query is to be able to specify a date range and return all incidents for that time period...
  11. D

    Importing Old DB into New

    I don't know how much information I can provide on here because it is law enforcement sensitive. And you're right you don't see a case column in my example because it does not exist in the old database. I don't know if this will explain it better: right now everything in my example is in...
  12. D

    Importing Old DB into New

    Greetings, At work I have inherited a database from a predecessor that is incredibly inefficient. In essence, it contains case information and subject information where there can be multiple subjects to one case. For example this is how it is entered: Date Location Subject Name...
  13. D

    Multi-Table Query Question

    Now that I've played around some more I can get them to line up much better. I thought maybe the subreport would snap to the parent report, like a subform does. Nevertheless I've got it to where I want it to be. Thank you again!
  14. D

    Multi-Table Query Question

    Hi there. I was successful using the subreports, but one thing I am having a hard time with is getting the subreport fields to line up with the original Person fields. In the example you provided it all looked very clean and lined up. How were you able to do that?
  15. D

    Multi-Table Query Question

    That one worked perfectly. How were you able to eliminate the SubjectID parameter?
Top Bottom