Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About NeuroPulse

  • Rank
  1. Wow. How did you figure that out so fast. I guess I didn't fully understand how reordering with a summary worked. Thanks.
  2. Greetings again -) Trying to get records to sort like this: Region, Price B, $6 B, $7 B, $9 C, $5 C, $6 C, $8 A, $4 A, $8 A, $9 That is, list the regions in order of which has the highest lowest price. The lowest price in B is $6 which is higher than the lowest prices in C and A. So I want to put the prices in order for each region, then put the regions in order according to the one with the lowest price. Can this be with Sort? BY using a summary field somehow? If not, with a summary report? Been struggling with it. Thanks
  3. Hi, This seems like it might be much faster than the self-joining whose calculations for a hundred thousand records is taking a very long time. Is there a way to create an item table from the itemIDs in the database? There are thousands of different items. Thanks
  4. I think I understand! -) What makes this work is that when, for a given field value, a corresponding value is looked up on another table, if there is more than one record with the given value, then the first record found is used. This technique is taking advantage of that, even though it does not happen that way for the purpose of doing this. It just has to pick a record and it picks the first match. Is that right?
  5. Hi. Did a search and found out about the help file entry called "Identifying duplicate values using a self-join relationship". Trying to use this to do want I want. Questions about it: 1- It says, "The primary record is the first matching record according to the sort order defined in the relationship." Can you explain what that means? How do you define a sort order in a relationship? 2 - In If(Counter = table1::Counter, "Unique", "Duplicate") what am I supposed to put for table1? Is that duplicate table created in the self relationship? Thanks Here is t
  6. Thanks. I misread his post. "(*) You are not supposed to remove all duplicates, but to omit all duplicates except one in each group. This is not a trivial task - that's why John suggested you look at some previous threads discussing various techniques to accomplish it."
  7. That is excellent. Thanks. I did not know about summary reports. But I need to be able to do this in table view so I can further manipulate the records from the results.
  8. Greetings, Trying to list just the records with the lowest price for each item and having much difficulty. Example records: ItemID, Price 1 $1 1 $2 1 $3 2 $1 2 $2 2 $3 I would want it to just list: ItemID, Price 1 $1 2 $1 omitting the others. Thanks
  9. Ah! That is the problem. I thought it would leave one record and return the duplicates of that record. I am trying to keep just one of duplicate records. "It returns all records that have a duplicate value.. e.g. if three records have the value "test" in the field "X" then all THREE records will be returned, not just two. That may be where you're getting confused? Given the volume of records I doubt it, but still worth mentioning."
  10. Greetings, When I use Find to find duplicates (records with the same value in the same field), it finds *far* more than the duplicates. I have about 100,000 records and it finds about 99,900 when it should find about 1000. I can't figure out what is going on. I click the find button and put an ! in the field I want to check for duplicates in. Help
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.