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

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

Lock error

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

    Lock error

    I need a little help. I've upgraded to A4V7 since I'm using XP now. I wrote a prescription application is now pretty well debugged and have used it for 6-8 years now. But now with A4V7, if I change a field in the parent datbase say "patient name" and try to save the record, I get an error, "Lock error Un-Locking. Pressing F10 4 times (each with a beep) allows me to force the error but no explanation as to what was "forced." One other clue, once when I changed a field and moved to another field before saving the record and then tried saving the record, I got an error, "key field changed, commit the record: yes no" However, I have been unable to duplicate that error since I made some attempts to look at linking fiels set structure and field rules. Sorry I didn't log my changes but the main problem still continues.
    Changing a field in the database alone (not part of a set is no problem. Any ideas? Am I risking data by forcing th error?
    Thanks to all who respond.

    Bob Slayden, M.D.

    #2
    RE: Lock error

    addendum; I just repeated my second error. By moving to another field with the cursor or enter and then pressing I get the second error "Key field changed commit the record: Yes no" pressing "y" or F10 gets beeps 4 tiems then the change is accepted (forced?)

    I also discovered that simply pressing "c" to change the record without actually making any changes and then attempting to save the record unchanged gives the same error.

    Thanks,
    Bob Slayden, M.D.

    Comment


      #3
      RE: Lock error

      anothe addendum: sorry

      I wrote, "I also discovered that simply pressing "c" to change the record without actually making any changes and then attempting to save the record unchanged gives the same error." This is true only once, if I press "c" and save twice, no error the second or subsequent times. This is only true if no data is actually changed.

      Thanks again,
      Bob Slayden, M.D.

      Comment


        #4
        RE: Lock error

        Check the referential integrity for the set you are using. You are changing the value of a field that makes up the referential intgrity rule. You may have to change the way the tables are linked (what common fields create the link).

        Comment


          #5
          RE: Lock error

          Charles,
          Thanks for the input. However, this occurs if I change the value of ANY field in the parent set. Also the referentegrity rule is based on a field, "Pt_number" that never gets changed. Any other ideas? Also, never had and still don't have a problem with A4V6.

          Comment


            #6
            RE: Lock error

            If you run without referentail integrity enforced, do you get this same problem? You might have a corrupted field rule since the field rules should see the no change entry as not a problem.

            Dave

            Comment


              #7
              RE: Lock error

              I finally uncovered the answer to my on question....its in Other>Configuration>Default section of A4V7. I set single step enters = "no" and Multi user mode = "no" and the problem went away. Auto flush = "yes" but I believe it was before.

              Comment

              Working...
              X