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

Incrementing character field and leading 0's

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

    Incrementing character field and leading 0's

    Thanks to Bill a Jerry's answer in a previous post I have been successful in auto incrementing a via x basic. I have run into one other problem. One of the fields that i need to auto increment was started off in about 20 applications with "000001". If the value starts with any zeros they are droped. Below are two working scripts but leading zeros are always droped.

    ''Script one
    dim temp_c as c
    t = table.open("inv_hdr")
    t.fetch_last()
    temp_c=str(val(substr(t.inv_no,1,7))+1,7,0)
    t.enter_begin()
    t.inv_no=temp_c
    t.enter_end(.t.)
    t.close()
    end

    ''Scritp two
    dim temp_c as c
    t = table.open("inv_hdr")
    t.fetch_last()
    temp_c = str(Val(t.inv_no)+1,7,0)
    t.enter_begin()
    t.inv_no=temp_c
    t.enter_end(.t.)
    t.close()
    end
    These scripts will also leave 2 or blank spaces to the left and right so if I start with "000001". The script ends up creating a value of " 2 ".
    Any ideas how modify either script to salvage the leading zeros
    Thanks, Jeff

    #2
    RE: Incrementing character field and leading 0's

    Jeff,

    Use something like this

    temp_c = padl(ltrim(str(Val(t.inv_no)+1,7,0)),7,"0")

    Regards,

    Ira J. Perlow
    Computer Systems Design & Associates
    [email protected]
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions

    CSDA Code Utility
    CSDA Screen Capture


    Comment


      #3
      RE: Incrementing character field and leading 0's

      Jeff,

      Use the padl (pad left) function to pad out the resulting string to the required length. The function allows you to the width of the result and the character with which to pad.

      Hence, from the interactive window:
      temp_c = "2"
      temp_c = padl(temp_c,7,"0")
      ?temp_c
      = "0000002"

      I had to do a lot of this sort of manipulation in order to take a course section number and augument it in order to generate a default for the next section which I could check for uniqueness (since you can't have two course sections in the same term with the same number). What made the problem difficult was that the section numbers sometimes contain non-numeric characters, (eg. to distinguish between a class and a lab). I had to remove these, increment the number, and then reinsert the non-numeric character(s).

      It got a bit gothic.

      This leads me to another suggestion which is rather obvious. You might want to consider creating a function to do the increment. It really cleans up your code and makes it easier to understand.

      For example, when I want to generate a course section I need only write

      next_section(previous_section)

      since the two pages of heavy lifting to create the new number are in the custom function called "next section".

      Bill
      Bill Hanigsberg

      Comment

      Working...
      X