Alpha Video Training
Results 1 to 11 of 11

Thread: HEAP LOCK error prevents updates to a table

  1. #1
    Keven Thibeault
    Guest

    Default 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. #2
    "Certified" Alphaholic
    Real Name
    Peter Wayne
    Join Date
    Apr 2000
    Posts
    1,728

    Default 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 http://www.learnalpha.com/HeapLock/HeapLockErrors.htm for a more detailed explanation.

  3. #3
    Keven Thibeault
    Guest

    Default 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. #4
    Steve Dentler
    Guest

    Default 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. #5
    "Certified" Alphaholic
    Real Name
    Peter Wayne
    Join Date
    Apr 2000
    Posts
    1,728

    Default 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. #6
    Keven Thibeault
    Guest

    Default 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. #7
    "Certified" Alphaholic
    Real Name
    jim chapman
    Join Date
    Apr 2000
    Posts
    1,779

    Default 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. #8
    Keven Thibeault
    Guest

    Default RE: HEAP LOCK error prevents updates to a table

    THanks jim

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

    thanks again

  9. #9
    Steve Dentler
    Guest

    Default 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. #10
    Keven Thibeault
    Guest

    Default 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. #11
    "Certified" Alphaholic
    Real Name
    Peter Wayne
    Join Date
    Apr 2000
    Posts
    1,728

    Default 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.

Similar Threads

  1. Error Message: "heap lock failure"
    By Jerry Jalbert in forum Alpha Five Version 5
    Replies: 2
    Last Post: 07-22-2004, 03:02 AM
  2. Heap Lock Error
    By dchiass in forum Alpha Five Version 4
    Replies: 1
    Last Post: 04-15-2004, 01:40 PM
  3. Heap Lock Failure error. Why?
    By Joseph Cincotta in forum Alpha Five Version 5
    Replies: 2
    Last Post: 04-02-2003, 04:18 AM
  4. Got a heap lock in v4.5...
    By Stephen Williams in forum Alpha Five Version 4
    Replies: 0
    Last Post: 03-10-2001, 12:35 PM
  5. Heap Lock Failure
    By richardurban in forum Alpha Five Version 4
    Replies: 5
    Last Post: 12-21-2000, 04:58 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •