Search results

  1. S

    Report from Query(ies) issue

    I'm reading up and learning about grouping by clause, it seems exactly what I need, thank you for pointing me in the right direction.
  2. S

    Report from Query(ies) issue

    I do not know which formula to use to have the query just sum up the intCourtdays for those that have the same CaseID, and not the others intCourtdays of other CaseID. example of data: Case ID (from [tblCase]) / intCourtDays (from [tblHearing]) 1 / 0.5 2 / 0 3 / 0 4 / 1 5 / 4 5 / 2 6 / 4 I...
  3. S

    Report from Query(ies) issue

    I'm going to try that! thank you
  4. S

    Report from Query(ies) issue

    Hi guys, I'm building a report based on a query, so far I have everything I need except for one field. (here is a summary of current state) Here is the query so far (information from 2 tables) SELECT [strLastName] & "." & Right([ServiceNumberID],3) AS [Name of case], tblmember.strRank...
  5. S

    Forms dealing with many-to-many junction table

    Your idea works brilliantly!!! either with records already there or to associate new charges to member(s)! Thank you so much! Now that I understand this, I'm trying to make this more user friendly. in most cases (pun intended) there is only one member per case (joint trial are fairly rare, 1...
  6. S

    Forms dealing with many-to-many junction table

    I found an article that shows how to do this, I'm trying to duplicate the results!
  7. S

    Forms dealing with many-to-many junction table

    OMG if I had created a button through the wizard, it shows there! I usually create button from scratch
  8. S

    Forms dealing with many-to-many junction table

    I know this is a basic question but: How do you get the button to open on the active record? (I'm searching on how to do this, now) the Junction subform will show (if any) the records of the active charge to a member and have the option to add more association with other members. Now I have...
  9. S

    Forms dealing with many-to-many junction table

    Now I will try to do this! thanks for the guidance so far!!!
  10. S

    Forms dealing with many-to-many junction table

    "all records in the tblJunction related to that charge" is empty when the user is filling this for the first time, and all that tbljunction has is a bunch a number that the user will not understand (I do since they represent the chargeID and the memberID, but the user never sees those.
  11. S

    Forms dealing with many-to-many junction table

    I cannot picture how to do this. Would you create a query based on the tblmembers and also have tblJunction ChargeID and MemberID? then create a form based on that query?
  12. S

    Forms dealing with many-to-many junction table

    i think i'll put the sentence in the tblMember it makes more sense to me. Since there is one sentence per member (regardless of how many charges that member is accused of) by putting it under charge, I will have a record for a sentence attached to each charge, and I don't want that.
  13. S

    Forms dealing with many-to-many junction table

    what do you think of post #13?
  14. S

    Forms dealing with many-to-many junction table

    I put ysnChargesWithdrawn (meaning it is a yes/no field if all charges were withdrawn for this case) in the tblCase because I also wanted the datWithdrawn (date all the charges were withdrawn) besides datTerminated (which is the date the case is terminated when finding/sentence are given by the...
  15. S

    Forms dealing with many-to-many junction table

    Now, how to relate the tblSentence to this. A member gets one sentence per case (may have multiple sentences over time if he/she has multiple case) A case can have multiple sentences if multiple members on trial. (only one sentence per member) A case may have no sentence if findings = not...
  16. S

    Forms dealing with many-to-many junction table

    Edit: I wrote this post below at the same time you replied this post above^ If I understand this: each unique member entry (from tblMember) is related to a docket through the charge(s) assigned to him/her. strFinding (under tblJunction) is still under the proper table, since a finding...
  17. S

    Forms dealing with many-to-many junction table

    I took the screen shot, from the computer I work from, then transferred the screen shot on the computer that has internet to post to you, then realized I forgot to remove the extra relationship. This laptop does not have the updated MS Access, and other computer I work on access with, does not...
  18. S

    Forms dealing with many-to-many junction table

    tblCharge Charge Desig/NDAref/otherlaw/otherlawRef/StatementOfTheOffence/Alt? First Charge / 129 / - / - / Neglect to the prejudice of good order and discipline / - Second Charge / 129 / - / - / Conduct to the prejudice of good order and discipline / - Third Charge / 130 / 86(1) / Criminal...
  19. S

    Forms dealing with many-to-many junction table

    1. I decided to combine (again) the tblmember and tblmemberinfo, and in the end, there will be more than one record when a member is charge again, I will have very few duplicate, since it does not happen that often. One way to eliminate a problem, plus, this also resolve my issue if I had a...
  20. S

    Forms dealing with many-to-many junction table

    tblmember contains information about a member that does not change over time. tblmemberinfo contains other info (i.e. rank and unit) of the member at the time of a specific trial. If the same member gets charged again in 10 years, that member will most likely have a different rank and be at a...
Top Bottom