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

Missing contiguous numbers

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

    Missing contiguous numbers

    I am having brain fog.
    Situation;
    The cheque reconciliation process uses contiguous cheque numbers. The numbers are always contiguous as printed on the cheques.
    So I have a start Chq# of 1219 and an end Chq# of 1262 = 43 entries

    Problem is that there is one number missing in the middle. Chq# 1222.
    I would have thought that Last Chq# minus First Chq# allow for the missing Chq#, but it doesn't, using LAST(chqno) - FIRST(chqno)

    So has anyone solved the problem of missing or non-contiguous numbering, or can kick my soggy brain ito gear?
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    #2
    Was there a failed transaction ?
    Gregg
    https://paiza.io is a great site to test and share sql code

    Comment


      #3
      Was check 1222 deleted?

      Dave Mason
      [email protected]
      Skype is dave.mason46

      Comment


        #4
        Index problem?
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


          #5
          Attached is an example of the problem.
          No failed transaction, Gregg as it is a simple list
          Not been deleted, Dave as it was never entered
          Not an Index issue, Al as there isn't one. The order however is lowest to highest nunber

          Contig.zip ​​​​​​​
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment


            #6
            here's a brute force solution. preprocess the list. Doesn't try to do it in the report itself. -- tom
            Attached Files

            Comment


              #7
              My example req'd: adding field to your table; creating an index; creating a Fn() on code page; changes to form and report to match.

              Comment


                #8
                Originally posted by Ted Giles View Post
                I am having brain fog.
                Situation;
                The cheque reconciliation process uses contiguous cheque numbers. The numbers are always contiguous as printed on the cheques.
                So I have a start Chq# of 1219 and an end Chq# of 1262 = 43 entries

                Problem is that there is one number missing in the middle. Chq# 1222.
                I would have thought that Last Chq# minus First Chq# allow for the missing Chq#, but it doesn't, using LAST(chqno) - FIRST(chqno)

                So has anyone solved the problem of missing or non-contiguous numbering, or can kick my soggy brain ito gear?
                As Tom said - preprocess...

                So if you're looking for the count of a list that may have missing row(s), you should build a list of those check numbers <TBL>.RECORD_CONTENT_GET()
                and then use line_count() to get the count of the records in that list. That way you can have multiple rows missing and get the actual count.

                If you need to know the missing check numbers, then build a second list with all the values in your range and use WORD_SUBTRACT()
                to remove the numbers that exist from the list of all possible numbers.

                In a multi user system, list processing is the better way to work this rather than using tables.
                Al Buchholz
                Bookwood Systems, LTD
                Weekly QReportBuilder Webinars Thursday 1 pm CST

                Occam's Razor - KISS
                Normalize till it hurts - De-normalize till it works.
                Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                When we triage a problem it is much easier to read sample systems than to read a mind.
                "Make it as simple as possible, but not simpler."
                Albert Einstein

                http://www.iadn.com/images/media/iadn_member.png

                Comment


                  #9
                  This might not be wanted, but it appears some important information is being withheld.

                  This could be a minor error, but the math presented in the original post does not compute.
                  Code:
                  dim countit as C
                  dim howMany as N
                  countit = <<%txt%
                  1219
                  1220
                  1221
                  1222
                  1223
                  1224
                  1225
                  1226
                  1227
                  1228
                  1229
                  1230
                  1231
                  1232
                  1233
                  1234
                  1235
                  1236
                  1237
                  1238
                  1239
                  1240
                  1241
                  1242
                  1243
                  1244
                  1245
                  1246
                  1247
                  1248
                  1249
                  1250
                  1251
                  1252
                  1253
                  1254
                  1255
                  1256
                  1257
                  1258
                  1259
                  1260
                  1261
                  1262
                  %txt%
                  howMany = *count(countit)
                  debug(1)
                  Gregg
                  https://paiza.io is a great site to test and share sql code

                  Comment


                    #10
                    1222 is missing, you have it included.
                    Al Buchholz
                    Bookwood Systems, LTD
                    Weekly QReportBuilder Webinars Thursday 1 pm CST

                    Occam's Razor - KISS
                    Normalize till it hurts - De-normalize till it works.
                    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                    When we triage a problem it is much easier to read sample systems than to read a mind.
                    "Make it as simple as possible, but not simpler."
                    Albert Einstein

                    http://www.iadn.com/images/media/iadn_member.png

                    Comment


                      #11
                      So this is one option that works.

                      I would do all of the processing prior to the report, but this does as much as possiBle in the report.

                      It does require a UDF to generate the list of all possible checks.

                      Contig2.zip
                      Al Buchholz
                      Bookwood Systems, LTD
                      Weekly QReportBuilder Webinars Thursday 1 pm CST

                      Occam's Razor - KISS
                      Normalize till it hurts - De-normalize till it works.
                      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                      When we triage a problem it is much easier to read sample systems than to read a mind.
                      "Make it as simple as possible, but not simpler."
                      Albert Einstein

                      http://www.iadn.com/images/media/iadn_member.png

                      Comment


                        #12
                        Thanks all, it';s not as simple as one might imagine.
                        I was working on a warning displayed on the screen, and it works fine - still work in progress as they say - but a bit more fiddling to do.
                        You will need to believe me on this, but I came up with a different method to Tom, but it has the same effects.

                        Next job will be identifying the missing numbers - if there are several - and naming them.

                        Alpha 1 Numbers contig.pngAlpha2 chq missing.png
                        See our Hybrid Option here;
                        https://hybridapps.example-software.com/


                        Apologies to anyone I haven't managed to upset yet.
                        You are held in a queue and I will get to you soon.

                        Comment


                          #13
                          Crossed posts Al.
                          I will download and look tomorrow.
                          See our Hybrid Option here;
                          https://hybridapps.example-software.com/


                          Apologies to anyone I haven't managed to upset yet.
                          You are held in a queue and I will get to you soon.

                          Comment


                            #14
                            Originally posted by Al Buchholz View Post
                            1222 is missing, you have it included.
                            Al,
                            Ted stated cheqs labeled 1219-1262 = 43, but that statement is incorrect.
                            This is why I stated we are missing some information regarding cheq 1222.
                            Only Ted has that information right now.
                            Gregg
                            https://paiza.io is a great site to test and share sql code

                            Comment


                              #15
                              You have missed the point Gregg.
                              Last # minus First# is a correct calculation.
                              Problem is there is a missing cheque no.
                              Loot at Toms suggestion.
                              See our Hybrid Option here;
                              https://hybridapps.example-software.com/


                              Apologies to anyone I haven't managed to upset yet.
                              You are held in a queue and I will get to you soon.

                              Comment

                              Working...
                              X