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

Alpha Entry Error and World of Grief

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

    Alpha Entry Error and World of Grief

    I'm working with an Alpha 4v8 database in a XP environment.

    When accessing via a SET we have a variable that blows an error anytime you enter data or key past it. This only happens in the set and not when accessing the field directly through the DBF. I have tried manipulating and even removing the filed rule associated with this record to no effect.
    This is a 5 digit number field. No matter what I try to enter into the field I get the following error:
    ____________________________
    Warning
    Entry error: invlaid number or
    number does not fit in field
    Continue Help
    ____________________________

    The real problem with this is I'm creating a batch entry script and this error is preventing it from working. It bounces out the the main menu every time.

    Any ideas on what's wrong?
    Thanks!
    Last edited by BoRoche; 03-15-2013, 11:46 AM. Reason: Added info about script.

    #2
    Re: Alpha Entry Error and World of Grief

    It sounds like you have got an auto increment on the child table. This is bound to cause a problem. Remove it. Or, as the error message says, increase the size of the link field in the child table.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      Re: Alpha Entry Error and World of Grief

      Thanks for the response.

      Auto Increment would be in the Field Rules?
      Child table would be the .SET or DBF?

      Comment


        #4
        Re: Alpha Entry Error and World of Grief

        Hi Bo,
        Auto Increment would be in the Field Rules?
        Yes.
        Child table would be the .SET or DBF?
        Would be the child DBF table in the set
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment


          #5
          Re: Alpha Entry Error and World of Grief

          Keith,

          Thanks for clearing that up. I've checked and found the following:

          Under the SET:
          -All existing Field Rules are set to "Increment : None"
          -The Field Rule for the field causing the error has no impact on the error when I change/remove it

          Under the DBF containing the problem field:
          -All existing Field Rules are set to "Increment : None"
          -There is no Field Rule for the field causing the error

          I hadn't considered the idea that the field was too short considering that I knew it was 5 characters (##.##) and I was entering less than that. I took your advice and did the following:
          I added a digit to the field by reconfiguring the database. That fixed the problem.
          I removed the digit by the same method and, here's the interesting thing. The problem is still fixed.

          I am guessing that this indicates some conflict or corruption in the database that was overwritten in the reconfigure.

          Thanks again for your help.
          Bo

          Comment

          Working...
          X