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

File locking error

  • Filter
  • Time
  • Show
Clear All
new posts

  • File locking error

    Am running A5 Beta Build 1170. My client is running 1174 and he still has the problem.

    The attachment is a portion of the operational database where the error occurs.

    Before going on to step 2 CLICK on the Edit/Add cases BUTTON to verify that it does work on smaller cases. CANCEL out to come back to Enter Cases screen and go to step 2.

    To duplicate the error.

    FORMS tab - click on MAIN MENU
    1. Click on ENTER NEW CASES
    2. Click on the button that says "Click here to locate BillTo"
    3. BillTo Find screen popsup - Enter "M" then "U" and down-arrow to Muller Muller Richmond Harms and HIT ENTER
    Back to Enter Cases with MULLER
    Click on Edit/Add cases


  • #2
    RE: File locking error


    I've looked at your file twice. It's a complex app.

    Has the Edit/Add Case button ever worked correctly? I ask because you do things differently than I have seen, and I"m wondering if there are simple syntax errors here?

    In order to debug this I recommend you take each piece of the code and simplify it to the extreme and then verify that it's behaving as you expect, by writing messages to the trace window.

    Beyond that here are come comments and questions which hopefully will stimulate a fresh look.

    At one point you establish a pointer to a table in the set upon which your form is based.

    This isn't exact, but it's something like this:

    f = parentform:tables:Billto.this

    later you write a change to a field in the Billto table like this:

    f.tablename->fieldname = "new value"

    I don't this syntax is right. I would use

    f.fieldname = "new value"

    assuming f is a pointer to the table.

    I also don't see an explicit statement closing the called dialog form. This is required, since the form doesn't go away when the user closes it. See Ch 22 of the Xbasic reference Manual for details.

    -- tom


    • #3
      RE: File locking error


      Turn off referential intergrity for the set. This will fix that problem. A simpler way to duplicate is to click the complete checkbox after step 3. You will get a file locking error because of the referential integrity. Beware, this WILL lock your computer. Even CTRL-ALT-Del won't work.

      Tom makes some good points. Your methods to get and use table pointers are a little obtuse, although they do work. There are simpler and more obvious ways to get and use pointers. I have attached your database in a modified form. Check the scripts on the enter cases form to see some possible changes.



      • #4
        RE: File locking error

        By the way, A5V4.5 works exactly the same. I created a form using the same set and code on the buttons. If referential intergrity is turned on, you get the same error. The problem is the child summons_id field on the form. This is the child linking field. Whenever you make a change to the parent, the program tries has to lock and unlock each child record. You get an error "File Locking - record count excedds max - 512"

        A simple solution is to remove the field summon_id from the form and replace it with field with a form layout variable. Use the OnFetch event to set the value of the variable to the summons_id. Example on the OnFetch (form layout variable name "keyval"):

        keyval = summons->summons_id



        • #5
          RE: File locking error

          Jerry and Tom

          Thanks for your comments on the file locking problem. I have taken your suggestions to heart.