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
Devcon 2020 Goes Virtual! LEARN MORE >

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 Value Out of Range

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Numeric Value Out of Range

    What would cause any change to a record to produce the error message: Numeric Value Out of Range, besides the obvious? I've checked all field rules and find nothing unusual...in fact there aren't any ranges applied in the field rules. Also, any change I try to make to a record in this table, no matter the field, will produce the same error message.

    I just installed Alpha Five v4, but once ran into the problem in v3. I don't know how that problem was solved because I tried several things and it eventually went away. I've rebuilt the indexes, packed the database, checked all field rules.

    I am suspicious of the table being linked in a set of which the parent is also the look-up for a child. The set is there for producing reports. I've deleted each field from the look-up, individually, to see if that gets rid of the error message, but no luck.

    Anyone else have this problem?
    Thanks,
    Wanda
    Tags: None
    #2
    RE: Numeric Value Out of Range

    The usual culprit is trying to enter a number like 10 into a field only large enough to hold one digit, whether by posting, updating, etc.
    There can be only one.

    Comment

      #3
      RE: Numeric Value Out of Range

      Nope. But good try. I'm not really sure which field is causing the problem, to be honest - since changing anything in any field will produce the error message. I am getting the message while attempting to do a simple data entry of a 6 digit number into a 10 digit number field. Upon testing other fields to see if they could handle any changes, I learned that none of them can. This is a real stumper. I'm trying to remember if i've ever posted anything to this table, but I don't believe I have - and even if I had, seems I would have encountered the message then. I've been able to enter data into this table (obviously, silly me)without a hitch.
      Any other ideas?
      Thanks,
      Wanda

      Comment

        #4
        RE: Numeric Value Out of Range

        I just tried entering a new record and saved after each entry into a field. The hang-up is on a date field that is used in a calculated field that subtracts one date from another. When I figure out the problem, I'll post it.
        Wanda

        Comment

          #5
          RE: Numeric Value Out of Range

          i suspect that you have a calc field in your field rules.

          try turning off all of the calc fields, then turning them on one at a time to isolate the problem.

          Comment

            #6
            RE: Numeric Value Out of Range

            I've been able to narrow the problem down to 3 date fields and 2 calculated fields. Hope someone can give me a tip on how to solve the problem.

            Scenario: A person enters the program on 1/1/00 and has not yet exited the program. I successfully used this calculation in the field AGE_AT_ENTRY and ran re-evaluate fields, which worked fine and gave me correct answers:

            (ENTRY_DATE-DOB)/365

            I also created a calculated field to evaluate the person's age when they left the program:

            (EXIT_DATE-DOB)/365

            The whole record hangs up, now, when I try to change data in any field. One sloppy way around it is to delete the calculated fields and re-write them, periodically, and re-evaluate the field rules...but I'd rather have a more efficient way to handle it.
            Thanks,
            Wanda

            Comment

              #7
              RE: Numeric Value Out of Range

              Yup, you're right. I discovered the problem and posted it on this board. See my previous post. I had no idea one could "turn on and off" a calculation...how is this done?

              By the way - I LOVE ALPHA DATABASE MANAGEMENT software...have been using them since 1985 or 1986, and used DBMII before that. I'm honored that you're looking at all the activity on the board and took time to respond. Made MY DAY :)

              Comment

                #8
                RE: Numeric Value Out of Range

                I suspect you're having a problem with the
                (EXIT_DATE-DOB)/365 when EXIT_DATE is not yet entered. You are then calculating -DOB/365 and even Hawkings would have trouble with a "minus" date.

                How about if(exit_date>DOB,(EXIT_DATE-DOB)/365,{})

                I think the comment about turning off calculated fields only referred to removing them temporarily and replacing them one at a time.
                There can be only one.

                Comment

                  #9
                  RE: Numeric Value Out of Range

                  After reading your post more closely I see that you are computing an age, not a date with the calculation. I should have posted

                  if(exit_date>DOB,(EXIT_DATE-DOB)/365,0)
                  There can be only one.

                  Comment

                    #10
                    RE: Numeric Value Out of Range

                    By George, I think you're on to something, here :) You're right about the problem being when the EXIT_DATE field is blank...I had actually meant to mention it on my post(s). Your solution sounds reasonable to me. I will test it...I KNEW Alpha couldn't possibly be incapable of handling a calculation seemingly as simple as dealing with two date fields when one is empty.

                    Comment

                    Previous template Next
                    Working...
                    X