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



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

HEAP LOCK error prevents updates to a table

  • Filter
  • Time
  • Show
Clear All
new posts

  • HEAP LOCK error prevents updates to a table

    Alpha 4.5, multiuser mode, 3000 records, part of a set

    cant post or update table...

    any ideas????

  • #2
    RE: HEAP LOCK error prevents updates to a table

    Are you talking about a post or update operation? Most likely you have a filtered index or two and the post/update is changing a lot of records to include or delete them from the index.
    You can read for a more detailed explanation.


    • #3
      RE: HEAP LOCK error prevents updates to a table

      Yes.. thanks.. already read that.

      There are no filtered indexes... and the problem seems to be more prevelant with more users opening the table on the network at the same time.


      • #4
        RE: HEAP LOCK error prevents updates to a table

        Auto-increment fields can sometimes be a problem in a widely accessed table. Are you running with full referential integrity on? Remember, full RI will lock all the child records during an edit. If your users are changing a lot of records, you might consider turing A5's RI off and enforcing RI yourself.


        • #5
          RE: HEAP LOCK error prevents updates to a table

          Steve has a good point about referential integrity. I've never had a problem yet, though, with autoincrement fields in v4, and my tables have a lot more than 3000 records.
          Do you have a particularly large set? My general rule of theumb is that I'm doing something wrong if a set for data entry has more than 3 tables. Sets for reports can be as complex as you like, although the more complex they are, the longer the report will take to generate.

          - Peter


          • #6
            RE: HEAP LOCK error prevents updates to a table

            My set has six tables...
            the table in question is the master of all. There is no referencial integrity, it does have an auto increment field (which in hindsight = totally unnecessary)

            one potentially unusual programming trick I do however = linking to the same child table FOUR different times, with the use of four filtered indexes.

            I had to do this because filtering records in a browse window on the form does not work

            here is the example: a parts database where some parts are new, others used:
            master record = part number
            child record = warehouse locations with qty, condition = NEW
            child record2 = warehouse locations with qt, condition = used

            I used filtered indexes here to replicate the filter I need

            THANKS everyone for your replies...


            • #7
              RE: HEAP LOCK error prevents updates to a table

              Hello Kevin,

              Watching this thread with interest.

              >>linking to the same child table FOUR different times, with the use of four filtered indexes.


              • #8
                RE: HEAP LOCK error prevents updates to a table

                THanks jim

                Will explore that.... didnt know about those functions !!

                thanks again


                • #9
                  RE: HEAP LOCK error prevents updates to a table


                  Interesting...only a heap lock failure...I would have bet that the server would have let off a puff of smoke as the memory chips caught on fire.


                  • #10
                    RE: HEAP LOCK error prevents updates to a table

                    I know... MS Win2000 Sever Ed = probably has a drinking problem now as a result !!


                    • #11
                      RE: HEAP LOCK error prevents updates to a table

                      Unless you have other reasons for what you are doing, there is really no reason to have 1 table for parts. You might as well have 2 tables, one for new parts, one for old parts. Then you would not have 2 filtered indexes. The only reason I can think of for having 1 table would be that it makes it slightly easier to see how many of something you have. But if you have a set:

                      master --> old_parts
                      --> new parts
                      both linked 1:many on the part_number, isn't this going to
                      work just the same as what you now have?

                      You could put both the browses on a form and still see all
                      the locations for any given part number.