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

Relation Exhausted

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

  • Relation Exhausted

    In the orders database, when clicking on "New RECORD" this error appears. Can anyone tell me what it is?

  • #2
    Re: Relation Exhausted

    Originally posted by NancyL View Post
    In the orders database, when clicking on "New RECORD" this error appears. Can anyone tell me what it is?
    Nancy

    I noticed that all of your other posts are in the A5v9 forum.

    Did this system move from A4 to A5v9?

    So many questions we must both have....

    I would check indices and/or rebuild them.

    Do you have a set with referential integrity turned on?

    Is there something about this order that is special? More lines, ....

    I noticed in the help file that it is error 1053.

    Does restarting Alpha eliminate the error?

    Can you post a sample that shows the error?
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.

    Comment


    • #3
      Re: Relation Exhausted

      We are going to from A4 to A5V9. It seemed that every time there was a patch it would create another problem. It is my understanding there will be no more patches! Yeah! I'm not as concerned about the errors as much as the cross overs. We thought it was fixed by saving the items regions before continuing the order but it hasn't. When multiple users are entering orders, we soon as one clicks NEW ITEM, they see the items from another user.

      Comment


      • #4
        Re: Relation Exhausted

        This is an old post but also the only one related to the query I did on Relation exhausted Error

        I dont' really see a resolution posted on what this error is or how to fix it, but our organization just ran into the same problem.

        Just finished installing a patch upgrade and now when users try to enter new records, they get a "Relation exhausted" error and it does not allow for new records to be entered.

        Is there any updates on this error or what it is related to.

        Comment


        • #5
          Re: Relation Exhausted

          In case anyone runs into this error, it has something to do with indexes.
          I've rebuilt all indexes and the error seems to have gone away

          I suggest that a constant maintenance be performed on your data by rebuilding indexes on a regular basis.

          Probably nothing new for most users, but I tend to learn things the hard way :)

          Comment

          Working...
          X