New call-to-action
Results 1 to 5 of 5

Thread: File Locking Error

  1. #1
    Ronald Frias

    Default File Locking Error

    I'm in the process of converting an Alpha 4 application to the current release of A5V5. The set consists of 4 DB files with cascading links. These files contain data placed by A4V6.2. After creating a new set form, I tried to edit an existing record and got an unrecoverable error.
    "File locking record count exeeds max: 512". I have addressed these limitations in A4 but I can't find how to increase this limit in A5V5. Any suggestions?

  2. #2
    "Certified" Alphaholic
    Real Name
    Tom Cone Jr
    Join Date
    Apr 2000

    Default RE: File Locking Error

    Ronald, I recall a similar message thread in the Version Four forum. Here's what Dr. Wayne said over there:

    Msg ID: 40652
    Subject: RE: Is this a
    Author: Peter Wayne
    Date: 05-04-2001 6:24 AM

    When you change a parent record in a set with referential
    integrity enforced, a5 has to lock all the child records.
    you have probably run into the limit of the number of
    child records that can be locked at a time.

    it is rarely necessary to use referential integrity in
    your sets. if you keep the user from ever changing the
    linking keys then it is not necessary to use r.i. and your
    application will run much faster, since you free a5 of
    the overhead of locking child records.

    If you're designing for a multi-user network setting you really don't want to lock all four of the tables in your set, and all the linked child records, when the user starts to edit the parent table do you? I would think your users would howl at being locked out of so many records. If you're not familiar with the collection of articles at I recommend it to you. There's a good one on point called 'Simplify Your Application Design' which might be of much help to you.

    -- tom

  3. #3
    Ronald Frias

    Default RE: File Locking Error

    Hi Tom,

    Thank you for your thorough analysis.

    I have only two reasons for using referential "enforced". First one is to have the key fields fill in automatically when creating new child records. Second one is to change, in one step, all "child" key fields if I should need to change the parent's key field.

    Are there other ways to accomplish the same? Do you think it is practical to turn on/off the referential setting when key field changes are needed?


  4. #4
    "Certified" Alphaholic
    Real Name
    jim chapman
    Join Date
    Apr 2000

    Default RE: File Locking Error

    Hello Ron,

    In general you should never change the linking field of the parent. The linking field value should not be part of your data. It should be a unique value divorsed from any of your data. This is what the auto incremented field rule can be used for.

    Even without referential integrity, child records added while in the set will 'inherit' the parent's linking value.

    Good Luck,

  5. #5
    Ronald Frias

    Default RE: File Locking Error

    Hi Jim,

    Thank you for your interesting suggestion.

    Is there a field rule that defines a child's (non-key)field value to be the same as it's parent, such that when you change the parents value, it will also change the childen's value in one step?


Similar Threads

  1. File locking
    By Roger Evans in forum Alpha Five Version 5
    Replies: 1
    Last Post: 05-12-2004, 09:32 AM
  2. Help! Error file locking record count exceeds 512
    By David LITTLE in forum Alpha Five Version 5
    Replies: 2
    Last Post: 02-18-2003, 06:53 AM
  3. File locking error
    By DonWalton in forum Alpha Five Version 4
    Replies: 4
    Last Post: 06-21-2002, 07:58 AM
  4. File locking error message
    By David Montgomery in forum Alpha Five Version 4
    Replies: 5
    Last Post: 05-04-2001, 07:06 AM
    By MARC DUVALSAINT in forum Announcements
    Replies: 0
    Last Post: 01-18-2001, 08:02 PM


Posting Permissions

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