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

Checksum Algorithm for Code128

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

  • Checksum Algorithm for Code128

    Has anyone ever written an Xbasic script for calculating Modulo 103 checksums on Code128 barcodes? If you have and wouldn't minde sharing the code, I'd be grateful. If you can pint me in the right direction, that would be nice too.

    Searching produced no results, and the checksum function in A5 v5/6 doesn't do Mod103.

  • #2
    RE: Checksum Algorithm for Code128

    I did something way long ago that's in the code archive, search for code 128. If I remember correctly I only implemented it for an even number of characters in the input string as I was working with encoding twelve digit upc numbers.
    There can be only one.

    Comment


    • #3
      RE: Checksum Algorithm for Code128

      And I just adapted this from something I found on the net.

      FUNCTION cksm128 AS C (input_string AS C )
      '*
      '* Initialize running total with value of start character, then scan the
      '* string and add character value times position
      '*
      SUBTOT = 104
      FOR I = 1 TO LEN(input_string)
      C = SUBSTR(input_string, I, 1)
      X = asc(C) - 32
      SUBTOT = SUBTOT + (X * I)
      NEXT I
      '*
      '* Calculate Modulo 103. This is the checksum
      '*
      cksm128= MOD(SUBTOT,103)
      '*
      '* Now convert numeric checksum to a character. This conversion takes
      '* into account the particular mapping of the font being used (this
      '* example is for the font published by Azalea Software).
      '*
      ''select CASE
      '' CASE CHKDIG = 0
      '' CHKCHR = CHR(174)
      '' CASE CHKDIG " 94
      '' CHKCHR = CHR(CHKDIG + 32)
      '' OTHERWISE
      '' CHKCHR = CHR(CHKDIG + 71)
      ''ENDCASE
      ''*
      ''* Now format the final output string: start character,
      ''* data, check character, and stop character.
      ''*
      ''OUTSTRING = CHR(162) + MYSTRING + CHKCHR + CHR(164)
      END FUNCTION


      I left in some other parts than the checksum "value" which you might be able to use. Usage is

      ? cksm128("BarCode 1")
      = "33"
      There can be only one.

      Comment


      • #4
        RE: Checksum Algorithm for Code128

        The function in the archive is limited to subset C while I think this one handles B and C.
        There can be only one.

        Comment


        • #5
          RE: Checksum Algorithm for Code128

          Stan:

          Thanks for your help. This will get me started.

          Comment


          • #6
            Re: Checksum Algorithm for Code128

            I notice that the checksum formula states the the Code 128 start character is 104 and the value of 104 is used in calculating the checksum. Why does the routine then use CHR(162) as the start character instead of CHR(104) ?

            I am having trouble generating readable code128 barcodes in some cases.

            I have also seen this checksum calculation shown as

            if 0 then 194
            else if < 64 then +32
            else +100

            instead of

            if 0 then 174
            ekse uf < 64 then +32
            else +71

            Why are there two different formulas?

            Any help would be appreciated.

            Thanks.

            Paul

            Comment


            • #7
              Re: Checksum Algorithm for Code128

              '* Now convert numeric checksum to a character. This conversion takes
              '* into account the particular mapping of the font being used
              (this
              '* example is for the font published by Azalea Software).
              There can be only one.

              Comment


              • #8
                Re: Checksum Algorithm for Code128

                I think this passage concerning generating Code 128 barcodes in .NET may be helpful.

                Comment

                Working...
                X