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

Announcement

Collapse

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

Finding numbers not in a sequence

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Finding numbers not in a sequence

    Is there a simple way of finding the next sequential number which is NOT in a number field of a table.
    eg. There is a table, with numbered field in each record. Sometimes the number sequence is skipped,
    (record 1 No field = 1, rec2 = 2, rec3 = 3, rec4 =5, rec5 = 7)
    I want a method of making a list of those missing numbers, in this case 4 and 6, in their sequence. Would posting the missing number, if it didn't follow the previous, to a different table be a reasonable idea ?

    Brian.

    #2
    RE: Finding numbers not in a sequence

    Brian, I can't think of a really easy way to do what you describe. Your approach will work if there is only one missing number in the gap between the current record and the previous record, and provided the table is sorted on the number field. Otherwise it will miss some, or so it seems to me.

    A brute force approach would:

    - sort the table on the number field
    - fetch the first and fetch the last, and use them to create
    an array with lower bound equal to the first value, and an upper bound equal to the last value
    - fetch the first
    - fetch each until you hit the last, examining the number field value each time and setting flags in the array elements that stand for missing numbers

    Databases are wonderful things but some of the hardest things I've had to design are reports that list information that's missing from a sorted table. Identifying what's 'not there' is a lot more difficult than reporting on what's stored in the database.

    -- tom

    Comment


      #3
      RE: Finding numbers not in a sequence

      Another brute force method is to create another table with just a field for the numeric values and then fill the new table with every possible value with no skipped numbers. Then subtract the first table which may have missing numbers from the table with all of the numbers. The subtract operation has a filter option, so you can set the filter to just check numbers equal to or smaller that the largest number in the first table. The result will have just the "missing" numbers.

      If this is something that must be done frequently, the table with the numeric test field only has to be created once, as long as enough records are included to cover future possibilities. Since it is only one field, it probably won't take much space.

      Jerry

      Comment


        #4
        RE: Finding numbers not in a sequence

        It seems that adding a child table, one to many, and sorting the parent
        on the no_field, then writing no_field_child when observing the parent
        for previous value +1.
        efs

        Comment


          #5
          RE: Finding numbers not in a sequence

          I have done a similar task where I had to identify the skipped sequence record and review each one to take certain corrective action. Fortunately, the table was not a large one.

          I had added a temporary 1-character field in the table. Then sort the table by the sequence number field. Using an update operation, if the difference between the current record sequence number and previous record sequence number (previous() function) was greater than 1, I would update the temporary 1-character field with "X" Once the operation was completed, I review the table in browse to make correction. It was tedious to make correction but it worked. I hope this helps.

          Eugene

          Comment


            #6
            RE: Finding numbers not in a sequence

            Brian:

            I believe there is an article in LearnAlpha.com by Barry Rochford "Finding Missing Numbers within a Sequence"

            It sounds like it may apply to your needs.

            I hope this helps.

            bob adler

            Comment


              #7
              RE: Finding numbers not in a sequence

              Thanks everbody for your inputs. I had this in A4, and used a search/sort to do more or less what has been suggested above. Just didn't want to miss any better way of doing it.

              Thanks for the ideas and responses. Most useful.

              Brian

              Comment

              Working...
              X