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



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

trailing spaces- duplicate check calculated field

  • Filter
  • Time
  • Show
Clear All
new posts

  • trailing spaces- duplicate check calculated field do we remove trailing spaces. Example:
    B72 /H00-P0/T24 - this a calculated product_id code
    (all character fields - width is 4 digits).
    When width value is 4 digits the display is perfect:
    B1234/xxx-xxx/xxx but when 2 digits it appears as above.
    Would like it displayed as:
    B72/H00-P0/T24 (no trailing spaces after 72 and have no problem with
    the code after the stroke)

    Tried trim/ltrim/ also remspecial everywhere
    Remspecial(filmtype+width+"/") - this removes the strokes.
    Filmtype+(remspecial(width))+"/" - does not work.

    Besides looking strange - operators are having difficulty using
    `find by key` as they forget to but 2 spaces in case of 2 digits. we check for duplicate record on the above calculated field.
    Tried: KEY_UNIQUE("product_id") onsave event..
    nothing happens and accepts duplicates

    Would appreciate some help on this.

  • #2
    RE: trailing spaces- duplicate check calculated fi

    Alltrim(expression) removes leading or trailing spaces, rtrim(expression) removes trailing spaces, ltrim(expression) removes leading spaces.

    You want:


    if I understand that you don't want trailing spaces after filmtype or width.
    There can be only one.


    • #3
      RE: trailing spaces- duplicate check calculated fi

      dear mathews,
      thanks your response.

      i do not want the trailing space after the width and just before the
      first stroke. that is, in case width is 2 digits - would want the
      stroke to move to the left and remove the 2 spaces gap so the code
      is displayed as a continuous code (without any gaps).

      forgot to mention tried alltrim also - what is irritating is that
      when evaluating the expression the display is as required -
      all continuous without gap but on the form it appears with 2 blank
      spaces after width in case of 2 digits..



      • #4
        RE: trailing spaces- duplicate check calculated fi

        The only thing I can think is that when you say "on the form it appears with 2 blank spaces", it must not be the calculated field you have constructed with alltrim() or rtrim().

        Do you have a table level calculated field that is being displayed and have you changed this calculation as well?

        Do you have more than one form level calculated field, as you tried to construct the correct concatenation, and are you using one of the "older" versions of your construction?
        There can be only one.


        • #5
          RE: trailing spaces- duplicate check calculated fi

          Example attached.
          There can be only one.


          • #6
            RE: trailing spaces- duplicate check calculated fi

            thanks.. hwr, just cannot get to work.. this is the full expression in
            field rules..(need to have it in field rules instead calculated on a
            form for lookup purposes in other tables).
            wonder what is wrong after width (width_in_char).



            • #7
              RE: trailing spaces- duplicate check calculated fi

              Without knowing your field definitions (width) and whether all are filled .......

              You are missing one right parenthesis



              chance of trailing spaces here
              and here

              +SUBSTR(MICRON_IN_CHAR,2,3))+"/" what if MICRON_IN_CHAR = "3 "

              Would change all "trim" functions to alltrim and see what happens and would say


              and alltrim(SUBSTR(MICRON_IN_CHAR,2,3))
              There can be only one.