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

numeric field bug

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

    numeric field bug

    I think this is a bug
    If you have a numeric field with 0 decimals and for example with a width of 7 characters, and you want set the display format to "12,345,678"
    On a form it works fine, but on a browse if you set the width to 7 and all 7 characters are used the value doesn't show up correctly it only shows as boxes, and if you set the width to 9 it lets the user fill in all 9 characters and returns an error "property not found"

    Thank you,
    Daniel Weiss
    Daniel Weiss
    EZ Link Software

    #2
    RE: numeric field bug

    Daniel:
    I just tested it. It works just fine. Make sure you have a named (not default) browse

    Comment


      #3
      RE: numeric field bug

      John
      I don�t know what you tested, please try the following
      Open Alpha sports and edit the quantity filed of the browse in the invoice form set the format style to 123,456.78, width to 7, decimals places 0, change to view mode and type 7 digits in the quantity filed go to next field and see what happens. Now change back to edit mode and change the width to 5, change to view mode and type 5 digits in the quantity filed go to next field and see what happens. Copy the quantity filed to the form itself and set the format style to 123,456.78, width to 5 or more, decimals places 0, change to view mode and you will notice it won�t let you more then 5 digits and the comma will show in correctly.
      By the way I just noticed that in a numeric field with decimals more then zero it has the same problem on a form also
      Thanks
      Daniel Weiss
      Daniel Weiss
      EZ Link Software

      Comment


        #4
        RE: numeric field bug

        I think your problem is that you are trying to put 7 digits in a 5 digit field. i.e. 7# of (*&% in a 5# bag. If you want 7 digits, change the structure of the field to 7

        Comment


          #5
          RE: numeric field bug

          No John
          All I want it is to work like on the form, it should not let the user type more digits then the width of the field is set to, and it should show up correctly as set in the format style
          Daniel Weiss
          Daniel Weiss
          EZ Link Software

          Comment


            #6
            RE: numeric field bug

            Daniel

            While your explanation is confusing, you have identified a problem.

            The numeric field is defined as a width of 5 and no decimals in table structure.

            In the embedded browse, the width is initially set as 5 and no formating.

            If you enter 5 digits in the column on the browse, you get a message the "data value can not fit in numeric size of field" Why, because the field structure width of 5 includes the comma, which means only 4 digits.

            If you apply the formating 123,456.78 to the column and leave the width to 5, it works correctly with 4 digits and gives the message with 5 as expected.

            Now, the problem occurs if you set the width of the column to greater than 5.

            Set the width to 6 with formating set to "none".
            Enter 6 or more digits. You get the message "Property not found" which really doesn't make much sense.

            I do think that this might be something Apha may need to correct as some formating (Dollars formating for checks) would require a much wider width than the field width to allow the whole text to appear and a user could enter too many digits.

            Solution, set the column width to the same width as the field width. Or increase the field width in structure to a width that is wider than any expected number. If you might sell 10,000 wigits, set the numberic width to 8 or 10.

            Jerry

            Comment


              #7
              RE: numeric field bug

              Jerry; Thanks for your explanation
              I think I found a simple and solid solution for this problem
              Set a Conditional mask style in the field rules as follows; (note you cant use a simple mask in a numeric field)

              For a filed with a width of 5 characters and 0 decimals places
              Set the mask to 00000 and the Condition to .t.

              For a filed with a width of 5 characters and 2 decimals places
              Set the mask to 00.00 and the Condition to .t.

              This way it will work correctly with any formatting you use on a form or browse just remember to increase the width of the filed on the formatting of the form or browse to allow space for the format characters

              Enjoy
              Daniel Weiss
              Daniel Weiss
              EZ Link Software

              Comment


                #8
                RE: numeric field bug

                Well I guess I was wrong
                It works fine for a numeric field with no decimals places, but it is no good for a numeric field that has decimals places, for example; For a filed with a width of 5 characters and 2 decimals places
                If you want to enter an amount with only one digit before the decimal (1.25) you will need to type a zero before the first digit (01.25) which is not acceptable
                Maybe someone could find a better solution
                Thanks
                Daniel Weiss
                Daniel Weiss
                EZ Link Software

                Comment

                Working...
                X