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

Barcode Generation

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

  • Barcode Generation

    I have a stock table with numeric stock codes eg 1234, 78901 etc.

    I created a label report to print the stock codes using a barcode font for EAN barcodes.

    However the scanner does not recognise what is printed.

    This seems to be because the barcode needs to be in a set format.

    Does anyone know what is the correct format and how to generate it? It appears to be 13 characters with a checksum of some sort at the end and various spacer characters as well.

    A search of the forum did not reveal much in this area. If no-one know how to generate the correct format, does anyone know of a 3rd party DLL or the like which can be called to reply with the format which could then be stored in the table for label report to print?

    I know that some of this is beyond Alpha but there must be others who are beginning to look at barcode generation from Alpha?

  • #2
    Originally posted by metadyne
    I have a stock table with numeric stock codes eg 1234, 78901 etc.

    I created a label report to print the stock codes using a barcode font for EAN barcodes.

    However the scanner does not recognise what is printed.

    This seems to be because the barcode needs to be in a set format.

    Does anyone know what is the correct format and how to generate it? It appears to be 13 characters with a checksum of some sort at the end and various spacer characters as well.

    A search of the forum did not reveal much in this area. If no-one know how to generate the correct format, does anyone know of a 3rd party DLL or the like which can be called to reply with the format which could then be stored in the table for label report to print?

    I know that some of this is beyond Alpha but there must be others who are beginning to look at barcode generation from Alpha?
    EAN-13 is a superset of the UPC-A format. Try searching the board for UPC.

    Also a nice discussion here. Nothing here beyond Alpha.
    There can be only one.

    Comment


    • #3
      John,
      If after you set your barcode up as in the example Stan attached, and you still aren't able to read it, check your scanner's documentation. We use Metrologics scanners and a 3 of 9 barcode. We needed to prefix and suffix the numbers with "*" to get the scanners to properly read the code. Once we used the prefix and suffix, all went well.

      Good luck,

      Tom

      Comment


      • #4
        Originally posted by Stan Mathews
        EAN-13 is a superset of the UPC-A format. Try searching the board for UPC.

        Also a nice discussion here. Nothing here beyond Alpha.
        It appears that the built in Alpha function CHKDIGIT() will compute the EAN check digit if you use the upc flag

        Code:
        ? chkdigit("007567816412",2)
        = "5"
        There can be only one.

        Comment


        • #5
          According to what I have read I should start the barcode with 50 split 5 guard bar then 0 for the UK, followed by a 5 digit maker code, a centre guard bar, a 5 digit product code, a checksum digit and another guard bar.

          However the Alpha generates its own itemcodes by an auto-increment field rule c.f. an maker/product code set by the supplier

          So e.g itemcode=44758 would translate as

          5 - guard bar - 0 00000 - guard bar - 44758 - checksum 9 - guard bar

          Is this reasoning correct and how do I generate the guard bars from within Alpha?

          Comment


          • #6
            Originally posted by metadyne
            According to what I have read I should start the barcode with 50 split 5 guard bar then 0 for the UK, followed by a 5 digit maker code, a centre guard bar, a 5 digit product code, a checksum digit and another guard bar.

            However the Alpha generates its own itemcodes by an auto-increment field rule c.f. an maker/product code set by the supplier

            So e.g itemcode=44758 would translate as

            5 - guard bar - 0 00000 - guard bar - 44758 - checksum 9 - guard bar

            Is this reasoning correct and how do I generate the guard bars from within Alpha?
            If you study the upc_to_font() function in one of the posts on the subject you will note that the symbol is generated by appropriately "upshifting" the character to be printed. This is done by addiding a value to the character with the chr() function.

            Code:
            symbol[a] = chr(b+32)
            seems to generate the left guard bar, etc.
            There can be only one.

            Comment


            • #7
              Using a demo EAN font from IDAutomation, I was able to print an EAN representation of a upc "007567816412" with the attached function. Screen shot of barcode attached as well. IDAutomation maps the left and right guard bars to the "(" character and the center guard bars to the asterisk.

              The function would have to be extended to perform the correct mapping (encoding) for UK barcodes and any others that have a leading digit other than zero.

              There was a bit of trial and error and hardcoding of certain values in devising this so there well may be areas of the function that could be consolidated.
              There can be only one.

              Comment


              • #8
                Originally posted by Stan Mathews
                Using a demo EAN font from IDAutomation, I was able to print an EAN representation of a upc "007567816412" with the attached function. Screen shot of barcode attached as well. IDAutomation maps the left and right guard bars to the "(" character and the center guard bars to the asterisk.

                The function would have to be extended to perform the correct mapping (encoding) for UK barcodes and any others that have a leading digit other than zero.

                There was a bit of trial and error and hardcoding of certain values in devising this so there well may be areas of the function that could be consolidated.
                This should work for UK and Mexico as well as UPCs.
                There can be only one.

                Comment


                • #9
                  Many Thanks

                  The function seems to work - but with one issue which I can work around.

                  A product code of 57000 gives

                  ean_to_font("000000057000") = U(000000*PRKKKS(

                  Using the IDAutomation font you used, gives a wrong barcode as the capital U should be a small u.

                  However chr(117) used in the function does give a small u c.f. capital U so I am wondering why I get U?

                  Comment


                  • #10
                    Originally posted by metadyne
                    Many Thanks

                    The function seems to work - but with one issue which I can work around.

                    A product code of 57000 gives

                    ean_to_font("000000057000") = U(000000*PRKKKS(

                    Using the IDAutomation font you used, gives a wrong barcode as the capital U should be a small u.

                    However chr(117) used in the function does give a small u c.f. capital U so I am wondering why I get U?
                    Not sure. I don't know why IDAutomation uses the system they do for the first (un barcoded) digit of the country code which seems to appear for human readable purposes to the left of the actual barcode. The chr(85) "U" in the first version of the function I posted is a hard coded 0 for upc compliant usage. The second version of the function has chr(117) "u" for the UK 5 and chr(119) "w" for the Mexican 7.

                    Now I see. If you want to encode 57000 as a UK barcode, which it really isn't without a valid manufacturer code, you have to encode

                    500000057000, not 000000057000

                    the function doesn't know what country to encode for until you tell it. 000000057000 would be for US/Canada.
                    Last edited by Stan Mathews; 06-23-2006, 08:36 AM.
                    There can be only one.

                    Comment

                    Working...
                    X