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

Dealing with lock errors

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

    Dealing with lock errors

    Hi folks

    On a small network where the data is stored on a central server, machine 1 has to produce several daily reports which need exclusive access to the data. The other machines therefore receive lock error messages if they try to manipulate the data at the same time.

    Is there a way of testing to see whether a database is locked by a machine before other machines attempt to access the data?
    Something like "If the database you're about to access is locked by another machine, show a message saying come back later". How do I perform that test?

    I have experimented with shadow databases but it got a bit messy, and simple is always best...

    TIA
    Paul

    #2
    Re: Dealing with lock errors

    Paul,

    While the norm may be a locked report from what you are doing, if you have no pre-processed fields, widows or orphans, then the report will not be locked.

    If you do have that situation, then copy the needed records and report to a temporary copy on the local drive and process there. It will run there unlocked and often faster than running it in a shared method.
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions

    CSDA Code Utility
    CSDA Screen Capture


    Comment


      #3
      Re: Dealing with lock errors

      Thanks Ira, hadn't considered that option. Will experiment.
      Regards
      Paul

      Comment


        #4
        Re: Dealing with lock errors

        Hi Paul,
        A permanent cure to your problem is to disable the Opportunistic lock in your windows NT/2000/XP/2003 computers & servers. If opportunistic lock is enabled on these OS systems, it locks a file when a user opens it preventing others from manipulating the data or the file. This locking can sometimes damage the file or the index associated with the file. Opportunistic lock is a windows registry settings and can only be changed in the registry. If the Opportunistic lock is enabled the registry value is = 1, if it is disabled the value is = 0. If you need further assistance on how to change the Opportunistic lock within the windows OS registry feel free to let me know.

        RAWLINGS

        Comment


          #5
          Re: Dealing with lock errors

          Hi Rawlings

          I've seen the Opportunistic lock mentioned elsewhere, but we have manufacturing systems running on our network which need that locking to take place. I got round the problem by using a variation of Ira's suggestion - copying the relevant records to a new database on the server and processing from there, zapping the database when the work is done.

          Thanks for your input though - appreciated.

          Regards
          Paul

          Comment

          Working...
          X