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

"Data value cannot fit...." Huh?!

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

    "Data value cannot fit...." Huh?!

    This is a situation that I have not encountered after several years of Alpha use. I have a form in which is located a numeric field (size 8, decimals 2) in which I enter round numbers from 400 to 1000. In all records but one, I can enter any number without a problem. The problem is the one record: I can enter any number below 500, but not 500 or above. If I enter 500 or above, I receive the error message "Data value cannot fit into numeric field of size." This never happens with any other record in my database. I have looked into the db structure & field rules, but there are no limitations on the values that can be placed in the field. And there is no problem with the other records. I deleted the record causing the problem and entered a new record with the same data....and received the error message again! I would appreciate any idea of what is going on here.
    Tags: None
    #2
    Re: "Data value cannot fit...." Huh?!

    This is sometimes caused by a calculated field triggered on the data entry. Could be that some combination of field values in this record causes another field to be calculated to a result that it cannot contain.
    There can be only one.

    Comment

      #3
      Re: "Data value cannot fit...." Huh?!

      This particular field that has generated the error is indeed linked to a calculated field that adds up several fields. The error message, however, comes up only on this particular record which adds up to 950.00, well within the calculated field's size and specs. Many other records add up to greater than, lower than, or equal to, the 950 without any error message. I will dig into this record deeper to see if there is something out of the ordinary with the numbers involved in the calculation.
      Please read next reply: it is a clearer encapsulation of the problem.
      Last edited by fcajka; 06-19-2008, 09:44 PM. Reason: Clarification

      Comment

        #4
        Re: "Data value cannot fit...." Huh?!

        Upon further investigation, there are two calculated fields involved here. The first ("total_owed") is a simple sum of two fields, each a specific amount owed by a customer. The second subtracts the sum of payments (four possible fields labelled payment1 thru payment4) from the first calculated field. The problem appears to rise when the second calculated field has a remainder greater than 1049.80. There is no error message with 1049.80 or lower. I cannot figure why this would be the case. There is no place in my db tables or field rules for any limits. Nor am I aware of any limits in the expressions in calculated fields. How might this be possible?
        Last edited by fcajka; 06-19-2008, 09:43 PM. Reason: Better transition to clear up issues

        Comment

          #5
          Re: "Data value cannot fit...." Huh?!

          Originally posted by fcajka View Post
          Upon further investigation, there are two calculated fields involved here. The first ("total_owed") is a simple sum of two fields, each a specific amount owed by a customer. The second subtracts the sum of payments (four possible fields labelled payment1 thru payment4) from the first calculated field. The problem appears to rise when the second calculated field has a remainder greater than 1049.80. There is no error message with 1049.80 or lower. I cannot figure why this would be the case. There is no place in my db tables or field rules for any limits. Nor am I aware of any limits in the expressions in calculated fields. How might this be possible?
          I'd have to take a look at the table to see. Can you attach a sample. It wouldn't need any records other than one with instructions as to how to trigger the error.

          You did say that there were no field rules such as a post to another table?
          There can be only one.

          Comment

            #6
            Re: "Data value cannot fit...." Huh?!

            I've run into this a few time in the last few years. Many times it is because I was posting to a filed that was a calculated field in another table. The other problem occurred when I was appending from another table and the number in the source field was larger than the field in the entry table as I had defined it. Trying to append or post to a files that is defined as 10.2 N and the source field is 12.2 N will cause this error.

            Comment

              #7
              Re: "Data value cannot fit...." Huh?!

              Let me first thank you both for your interest in helping me resolve this problem.
              It was when I was reexamining the table to send as Stan requested with the "offending" record that I discovered the problem field. Since the field actually never is used in any form and I haven't really examined the table for several years, I had forgotten its existence. It needed to be adjusted from 6 to 7 digits. Inflation rears its ugly head!!
              Thanks again. Your efforts are very much appreciated.

              Comment

              Previous template Next
              Working...
              X