Databases
StackOverflow2013
Postsdbo
PODuplicate instances of records flooding my Access report
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODuplicate instances of records flooding my Access report
    primarykey
    data
    text
    <p>I'm having a duplication issue that I just can't figure out. Basically my report &amp; subreport are pulling a previous contributor list. What I need is for each instance of paid history to be grouped by the phone number and then the whole shebang sorted by date of the last sale. This is mostly happening except the problem is that for every instance of the sale, I am getting the full info returned. This is causing a lot of duplicates as you can imagine with the 10,000+ customers we have.</p> <p>So to be clear, in my example below I am getting the full phone number, name/address, and both sales in both places (based on date) in my report. I will see all of the info on both 1/4/2013 AND 6/6/2012. I don't want or need the instance at 6/6/2012 to show up, I only want it to show up alongside the 1/4/2013 sales. It still needs to have the 6/6/2012 paid history there, I just need the 2nd instance of it all to be eradicated.</p> <pre><code>555-1212 john smith 123 whatever dr hometown, usa 90210 sold date received date amount agentname 1/1/2013 1/4/2013 50 jack 6/1/2012 6/6/2012 25 jim 555-1212 john smith 123 whatever dr hometown, usa 90210 sold date received date amount agentname 1/1/2013 1/4/2013 50 jack 6/1/2012 6/6/2012 25 jim </code></pre> <p>My report is setup so the phone number, name, and address are all inside the PhoneNumber header and my subreport which contains the sold/received dates, amount, and agentnames is inside the detail section.</p> <p>Here's the query for my main report:</p> <pre><code>SELECT DISTINCTROW tblContributorsLead.PhoneNumber, tblContributorsLead.FirstName, tblContributorsLead.LastName, tblContributorsLead.Address1, tblContributorsLead.ZipCode, tblContributorsLead.CityName, tblPledgesLead.PledgeAmountRecd, tblPledgesLead.DateRecd FROM tblContributorsLead INNER JOIN tblPledgesLead ON tblContributorsLead.PhoneNumber = tblPledgesLead.PhoneNumber WHERE (((tblPledgesLead.PledgeAmountRecd)&gt;0) AND ((tblPledgesLead.DateRecd) Is Not Null)) ORDER BY tblPledgesLead.DateRecd DESC; </code></pre> <p>Here's the query for my subreport:</p> <pre><code>SELECT tblPledgesLead.PhoneNumber, tblPledgesLead.DispositionTime, tblPledgesLead.DateRecd, tblPledgesLead.PledgeAmountRecd, tblPledgesLead.Agent, tblPledgesLead.CampaignName, tblPledgesLead.Custom20 FROM tblPledgesLead WHERE (((tblPledgesLead.PledgeAmountRecd)&gt;0)); </code></pre> <p>I'd also like to say that this system was already in place before I took control, and I'm relatively new with access so any help will be greatly appreciated. I've moved every piece of this thing into and out of every section I can see and have tried a multitude of grouping and sorting options but to no avail.</p> <p>edit: here's a couple screenshots showing the issue. In the first screenshot I have circled a particular contributor. Notice the Date Rec'd column on each sale, that is the date they are being sorted by. The place that this contributor is at currently is where it should be, alongside the other sales from 9/23/2013. In the second screenshot you can see her full info listed again at the location of her previous sale, on 12/14/2010. This continues on for each and every date she has ever paid. This sale in particular will have 4 copies instead of just the one that I need. The one that I need should look identical to the one from 9/23/2013, containing all prior sale info alongside.</p> <p>First: <a href="http://i.imgur.com/5uRmyJ0.jpg" rel="nofollow">http://i.imgur.com/5uRmyJ0.jpg</a></p> <p>Second: <a href="http://i.imgur.com/APmEd2V.jpg" rel="nofollow">http://i.imgur.com/APmEd2V.jpg</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USepilimic
    1. USepilimic
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COCan you edit this question and attach a screenshot of your report to it? As it stands, I don't understand what it is that you **don't** want to see.
      singulars
      1. PODuplicate instances of records flooding my Access report
      1. USJohnny Bones
    2. COWell I'm not sure that a screenshot would help much more than what I've already posted above. Basically at every date in which there is a collected pledge for a customer, the entire block of info is duplicated. So if someone gives in march, july, and december i will see three full copies of his donation history (including all 3 of those paid dates). What I need is for it to ONLY show me the record alongside the sales in december since that would be the most recent sale. The record in december should also list the sales from march and july alongside, but in march and july I should see nothing.
      singulars
      1. PODuplicate instances of records flooding my Access report
      1. USepilimic
    3. COCurrently if I go to march or july I will see more copies of the same contributor including their history. This is essentially giving me 3 copies of the same contributor lead, which is a nightmare. I just need a single record showing all their payment history and it all needs to be grouped on the phone number and in sorted in order of most recent payment first. I'll go ahead and edit in a screenshot in a minute here.
      singulars
      1. PODuplicate instances of records flooding my Access report
      1. USepilimic
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload