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 A xbasic for button operation

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

  • UPC A xbasic for button operation

    This script was written to demonstrate a method only for converting UPC A bar code numbers into a printable format on any laser or ink jet printer. It is written to be used on a button. It is also in a format that will allow for simple modification to convert other types of bar code systems as they are all different. It does not have error checking or any extras. This was to make it easier to understand but it is fully functional and ready to go as long as these directions are followed. The script is meant to be edited by any user to fit his or her needs.
    This script assumes that you have a product table called product with two character fields. One named product_id (12 characters) and the other named bar_code (20 characters). I have also attached a font that should be copied to your windows fonts directory. Once you copy it you should open up the directory once and close it. For some reason windows does not seem to recognize until you do. After you have what you need to get started and want to test it out create a form on the product directory and drag an embedded browse onto it. You only need the product_id field and two instances of the bar_codes field in the browse. Set the font properties to one of the bar_code fields to "CIA UPC Truncated". This font should be available in your font selection if it was copied in properly. Set the font size to 20 and drag the vertical size of the browse rows down so they are about an inch. Add a button to the form with this script. The script is written to fetch the first record only and convert it demonstrating the conversion process. You will need to modify the script to fetch though you table and do all of you records at once or which ever ones you want. Open the form and type 12 characters into the product_id field and hit the button. If everything was set up as explained one of your bar_code fields should show the bar code output that we have all been paying too much for and the other should display the actual bar code in its scan form. This will work in reports as well as long as you set the font properties in the report to "CIA UPC Truncated". They will print on any laser or inkjet printer and can be filtered in full-page A5 reports or labels.
    Jeff Moses
    Interactive Information Systems, Inc.
    jeff@dealershipsoftware.com >any comments
Working...
X