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

Client side number formatting problem

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

    Client side number formatting problem

    Hi everyone and season greetings!

    I have a simple problem that I cannot figure out, so I appreciate any help.
    I have a UX form with a repeating section with one numeric field.
    The decimal point is (comma) and the thousand separator is (point) in the UX properties.
    Also the numeric field inside the repeating section, I have display format and client side format (both use the same settings as in the UX properties).

    So when I type 1000, after pressing tab the field is formatted as 1.000 (with point as thousand separator).
    THE PROBLEM is when I use javascript to getValue, the result is 1. I tried $u.decimal and $u.comma without success.
    If I change the field type from numeric to character works ok, but I want to use it as numeric field.

    Thank you in advance
    Vangelis

    #2
    Re: Client side number formatting problem

    Using version 5487 I'm not seeing your issue. I have a Textbox control with type set to Numeric. The Display format is...

    Code:
    formatCurrency(<value>,"",2,".",",")
    Client Side Properties Client side formatting is turned on, Format type is set to number and the Format definition is as you describe.

    A input value of 1000 results in 1.000 showing in the control and a .getValue returns "1.000" which is correct.

    There must be some other setting you're using or you're using an Alpha version other than 5487.

    Comment


      #3
      Re: Client side number formatting problem

      Hi David,

      I haven't upgrade to the latest. Maybe this was the problem.

      Thank you !

      Vangelis

      Comment


        #4
        Re: Client side number formatting problem

        Keep in mind that if you have a client-side calculated field expression you will need to put something like
        alltrim(str(((Item_Price * Item_Quantity) + product_cost),250,2,",")) in there as the calculation will wipe out a display format in the text box properties...
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment


          #5
          Re: Client side number formatting problem

          Hi again,

          The problem remains and let me summarize it:
          In UX form with decimal comma(,) and thousand seperator point (.) in the UX properties,
          and a field of type numeric, with display format alltrim(str( convert_type(<value>,"N") ,250,0,"B"))
          and client side formatting as the above : When I type 1000, the system displays 1.000 but getValue returns 1

          I solved the problem when I add in the client formatting "Round Value" with precision 1, so:
          When I type 1000 the system displays 1.000,0 and the getValue returns 1000,0


          Thank you again
          VK

          Comment


            #6
            Re: Client side number formatting problem

            Ok... thanks for re-iterating your settings... I was wrong because I didn't pay enough attention to your first post.

            The problem is with the UX Property Setting settings for Number format - decimal character and thousands character. With these set I can confirm what you're seeing.
            Code:
            Number format - decimal character set to comma
            Number format - thousands character set to period
            It looks like Alpha is performing a conversion on the data before you're getting it. This looks like a bug.

            As you say... entering 1000 displays as 1.000. Further, entering 1,000 displays as 1. This is correct.

            Without your rounding fix, entering 1.000,12 displays as 1.000,12 and the getValue is 1000.12

            So... with a decimal value being entered... Alpha behaves itself.

            Without the decimal value, Alpha takes your 1000 (or 1.000 displayed) and seems to apply a conversion to it resulting in 1... which is wrong in this case.

            Here's the odd thing. If you change your UX Properties to...
            Code:
            Number format - decimal character set to period
            Number format - thousands character set to comma
            it looks like Alpha now behaves. Entering 1000 will result in 1.000 being displayed... and a getValue of 1.000.

            The question is... what do you want to see as a .getValue... 1000 or 1.000?

            Comment


              #7
              Re: Client side number formatting problem

              I also discover you last strange finding
              As we are in EU and the decimal point is comma, and thousand separator is point, I would like to keep those settings compatible and the same, across the application.
              I think this litle trick solves the problem for now.
              I prefer to see 1000. But If I receive 1.000 , I can extract it with replace.
              Thanks again.

              Comment

              Working...
              X