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

decimal comma

  • Filter
  • Time
  • Show
Clear All
new posts

    decimal comma

    I have a grid with a detail view. Two fields with numbers with two decimals are well displayed in the main grid: 234,55 or when there is nothing behind the comma: 234,00
    However in the updatable detailview the numbers show as 234.55 or if there is nothing behind the comma as 234
    How do I get the two decimals in the detailview always behind the comma? I use the format: alltrim(str(<value>,250,2,",")) in the main grid as well as in the detailview...


    Sorry, double post, I posted in Appserver8 first, but I don't know if there is any difference in V8 and V9...

    Re: decimal comma

    Just wanted to give you question another chance--I always figure 4 days without an answer and most times there will not be one! Not that I will be the one to answer a web side question....

    A bit of confusion as to what exactly you are striving to obtain here though.
    How do I get the two decimals in the detailview always behind the comma? I use the format: alltrim(str(<value>,250,2,","))
    First the part in blue above....are you saying you do NOT want a period for the decimal but instead want a comma? format you used, at least on the desktop side, tells Alpha to used a comma for the thousands delimiter and a period for the decimal. And to say there can be up to 250 characters for a number....well... 19 is the limit in Alpha.

    If a comma is what you want, then maybe the following will be of use--it can be condensed but left it expanded so it can be more easily figured out with the two steps used.

    dim value as n
    dim fmt_num as c
    = "234,00"
    Even if no help, someone else may chime in now.
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau


      Re: decimal comma

      Thanks Mike,
      The formatting is done by just choosing one of the pre-defined formats from Alpha5 and works well in the main grid. I used the same pre-defined format for the fields in the detailview, but there it doesn't work.... (see image).

      I'll try with your suggestion, but I am very new with Alpha5webapplications so if I will have succes......


        Re: decimal comma

        anyone? I've been trying for hours now, but I seem to miss something...


          Re: decimal comma

          The reason we are confused, as Mike said, is that, given a number like 12345.67, the formula:


          will yield 12,345.67, not 12345,67.

          How are you getting your values to have commas (instead of periods) to seperate dollars and cents?

          If you are using alltrim(str(<value>,250,2,",")), then have you applied something to Alpha to make it behave differently?
          Steve Wood
          See my profile on IADN


            Re: decimal comma

            The problem seems to be solved, although I have no idea how.

            What I did was choosing display format for the field and than the pre-defined format: 123.456,78
            Choosing this gives automatically the code :alltrim(str(<value>,250,2,","))

            I did this for the fields in the main grid as well as the fields in the detail view. For the main grid it worked well as you can see in the image above. For the fields in the detailview it did not work...

            What I did now (being a bit desperate) was just starting all over again with a new database, and also I installed the last patch (from today).
            Doing exactly the same as described before it works fine now.... both the grid and the detailview show 1234,56. Which surprises me, because I
            understand from you that alltrim(str(<value>,250,2,",")) should not do that, but I can assure you that this is exactly what is show in in the displayformat box for the fields now....
            So I have nu clue what was the matter, but am very glad it has been solved. I don't really feel like changing it anymore, but am curious what could be the cause and howcome it works now with a wrong code... thanks for your support.


              Re: decimal comma

              Happened again... Decimal comma is ok in grid, but doesn't show in detail view. I think I now know the reason: everything is ok when I don't prefetch the data for detailview, as soon as I do the domma dissapears and a number ending on 00 (like 150,00) changes in 150 without any decimal seperator...

              For speed reasons I like to use the prefetch function. Based on what is said above anybody has a solution?



                Re: decimal comma

                Im having the same problem, when using lookup to get data from a table, they appair with period in stead of comma for decimal seperation.

                Example 17,5 shows up afterr lookup as 17.5 all my fields are formated as 1234,56 numbers ?? Any ideas how to change the format of a number when useing lookup to get data into field,

                Using V10,5 web application