Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Appending duplicate records to another db

  • Filter
  • Time
  • Show
Clear All
new posts

  • Appending duplicate records to another db

    how can i accomplish this? let's say a db has 3 duplicate records. i mark them and only 2 get marked so i can only append the 2 records. i would like to append all 3 records, not just the two duplicates. why you ask, because they are only duplicates in 2 fields. i need to compare some data in a third field. so i want the 3 records it the new db, with 3 fields.

    can this be accomplished with dupes or do i need to proceed in another direction?



  • #2
    RE: Appending duplicate records to another db


    I'm currently in the final stages of writing a dupe checker and I can tell you that it works great; you can do this with Alpha Five very neatly, but you have to write some XBasic code. You also will need to add a field to your table in order to find the surviving (unmarked) record in each dupe set.

    Add a numeric field called something like: DUPE_GRP(N, 6, 0). Once you have marked the duplicate records you then sort the table in DUPE_GRP + unmarked() order (note: not actual syntax).

    Next, go through the table finding the first marked record in each set. When the first one is found, go back up one record, add a number 1 to the DUPE_GRP field and continue to do so until each record in that set has been assigned the same DUPE_GRP number. Repeat the loop, adding 1 to the next set's DUPE_GRP number, using a counter, until you have gone through the whole table.

    Once that has been done, you can copy out all the dupes -- survivors and casualties alike -- to another table. Now that you have a DUPE_GRP flag for all records in each set of dupes, you can delete them, sort them, split them into survivor only and casualty only tables, etc.

    Good luck.


    Geoff Hollander


    • #3
      RE: Appending duplicate records to another db

      ok, geoffrey, i'll give that a try


      • #4
        RE: Appending duplicate records to another db


        this worked for me, you may want to see if it will work for your application.

        db fields example: date, time, card#, amount. i need to check for duplicate amounts.

        1. i marked duplicate amounts.
        2. i did an append to a new database, including all fields, of the marked records.
        3. then i did an intersect of the new database to give me all of the duplicate amounts in the original database and stored them in a 3rd database.
        now i have all duplicate amounts in a separate database that i can do my reporting with.

        let me know what you think



        • #5
          RE: Appending duplicate records to another db


          I'm glad you got things working. Your approach is a good one in that, whenever changing a table significantly, it's smart to work with outside or temporary tables.

          The only problem I would have using this approach for my application would be, because it is a utility program meant to work on any table thrown at it; that I never know, from table to table, what its structure and field characteristics are going to be.

          The only way I can do this (that I've thought of so far, anyway) is to copy in the table to a "working" table. The user, based on the selected operation, will then map certain types of fields currently comprising the working table.

          If, for example, the user is searching for near duplicate records based on a matchcode of: "first_name + last_name + address + substr(zip,1,5)", the user has to tell the program which fields hold the first and last name, address and ZIP Code information.

          The working file is already a temporary file in this case, so I'm kind of free to beat it up a little. Typically in merge/purge operations the steps are to define the matchcode and how closely you want the "suspects" to match, find and then mark the dupes, review and edit what has been found (disposition status and-or data), run a report showing survivor and casualy records and their disposition (after editing), and then saving the unique and survivor records to one file, the duplicate, casualty records to another file and, sometimes, outputting a copy of the complete file with the dupe flags (usually for later processing).

          But, of course, this can vary too. Skipping steps and being able to go back to and change previous setup options and rerun operations to get more accurate results all mean that I have to plan to handle record processing sequentially, both backwards and forwards, so that each operation lays some ground work for the probable next step.

          I think your solution is innovative and will certainly keep your data clean. (I guess it just goes to show, again, what a great product Alpha Five is.) Good job Gary, writing dupe checking code's not for sissies!

          Best regards,

          Geoff Hollander