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

UPC check digit calculation

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

    UPC check digit calculation

    I have an app using A5V8 and I need to add a check digit to a UPC barcode values where that check digit had been removed by someone else.

    I assume this would be done via an update. If I'm wrong let me know.

    I have some instructions and sample code (unfortunately it's in Visual Basic)

    How would I make it go? see instructions and sample code below

    Thanks in advance.

    UPC barcodes include a check digit. The UPC check digit is the 12th digit in the lower-right corner of the barcode. Here's how to calculate a UPC barcode check digit
    The last digit in a UPC barcode is a check digit based on the previous 11 numbers. Our example barcode data is "41234554321"
    Add up the numbers in the odd positions left to right. Multiple the result by 3. Add up the numbers in the even positions. Now add the first subtotal to the second. The UPC barcode check digit is the single digit number makes the total a multiple of 10.
    4+2+4+5+3+1=19 19x3=57 1+3+5+4+2=15 57+15=72 and 8 makes 80
    In VBA/Visual Basic it looks something like this:


    Dim checkDigitSubtotal As Integer ' check digit throwaway

    ' Valid input is 11-digits (no check digit), 12-digits (with check digit), or 14-digits (GTIN).
    Select Case Len(UPCnumber)
    Case 11
    ' do check digit calculation
    Case 12
    ' lets ignore your check digit & use ours
    UPCnumber = Left(UPCnumber, 11)
    Case 14
    ' GTIN input, strip leading 2 characters & last one too;
    UPCnumber = Mid(UPCnumber, 3, 11)
    Case Else
    ' error handling goes here
    End Select

    ' do the check digit
    checkDigitSubtotal = (Val(Left(UPCnumber, 1))) + (Val(Mid(UPCnumber, 3, 1))) + (Val(Mid(UPCnumber, 5, 1))) + (Val(Mid(UPCnumber, 7, 1))) + (Val(Mid(UPCnumber, 9, 1))) + (Val(Right(UPCnumber, 1)))
    checkDigitSubtotal = (3 * checkDigitSubtotal) + (Val(Mid(UPCnumber, 2, 1))) + (Val(Mid(UPCnumber, 4, 1))) + (Val(Mid(UPCnumber, 6, 1))) + (Val(Mid(UPCnumber, 8, 1))) + (Val(Mid(UPCnumber, 10, 1)))

    Azalea_UPC_A_checkDigit = Right(Str(300 - checkDigitSubtotal), 1)

    End Function

    #2
    Re: UPC check digit calculation

    Let Alpha do it for you....

    chkdigit()
    There can be only one.

    Comment


      #3
      Re: UPC check digit calculation

      That will calculate it for a single number, how would I calculate the check digit for 100K or more entries for a field in a table ?

      Comment


        #4
        Re: UPC check digit calculation

        One at a time, with an update operation.

        By one at a time I mean create an update operation on the checkdigit field and have the expression

        chkdigit(upccodefield)
        There can be only one.

        Comment


          #5
          Re: UPC check digit calculation

          I'm getting closer.

          An update of the "Data_SKU" field using this formula:
          chkdigit(data_sku,2) gives the proper check digit but deletes the first part of the UPC. For example: 11122233344 after the update gives only the correct check digit of 6.

          What I want to do is turn the 11122233344 into 111222333446 which is the full 12-digit UPC code.

          What am I missing here ?

          Comment


            #6
            Re: UPC check digit calculation

            John,

            Data_SKU = "11122233344"
            chkdigit(data_sku,2) ="6"

            complete_upc = Data_SKU+chkdigit(data_sku,2)
            complete_upc = "111222333446"

            Create that calculated field and print it.
            There can be only one.

            Comment


              #7
              Re: UPC check digit calculation

              It's still a bit odd.

              When I use that formula in the expression builder it shows the check digit separated from the UPC.

              For example 11122233344 as the UPC shows like this in the expression builder example: 11122233344 6
              see attached JPEG

              But it shows up in the table as 11122233344 without the check digit of 6 being included.

              Getting closer but still a bit stumped why this is happening.

              Comment


                #8
                Re: UPC check digit calculation

                Ever noticed the Alpha trim functions and wonder what they are designed to do?

                Instead of a data_sku field of 11 characters you seem to have one of 12 characters.

                Data_SKU = "11122233344 "
                chkdigit(data_sku,2) ="6"
                complete_upc = Data_SKU+chkdigit(data_sku,2)
                complete_upc = "11122233344 6"

                Data_SKU = "11122233344 "
                chkdigit(data_sku,2) ="6"
                complete_upc = Data_SKU+trim(chkdigit(data_sku,2))
                complete_upc = "111222333446"
                There can be only one.

                Comment


                  #9
                  Re: UPC check digit calculation

                  Well, I finally did it.

                  For some unknown reason, A5 added 10 blanks leading the check digit. This caused the combo-data length to become larger then the field length could support and it was truncated. I made the field longer and could see both UPC and check digit within the same field but with blank spaces between the UPC and check digit.

                  I used this expression in the calculated field to combine fields and clean it up:
                  REMSPECIAL(DATA_SKU+TRIM(CHKDIGIT(DATA_SKU,2)))

                  Thanks Stan, I wouldn't have got here without you.
                  Last edited by John Cunradi; 01-26-2010, 02:52 PM. Reason: new info

                  Comment

                  Working...
                  X