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



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

Append operation in a multi user setting

  • Filter
  • Time
  • Show
Clear All
new posts

  • Append operation in a multi user setting

    The help doc says when an Append operation is triggered A5 locks the master file. Does it mean if user1 is in the midst of appending a set of records (SalesRep=John), user2 cannot append a different set of records (SalesRep=Fred) to the same master table?

  • #2
    Re: Append operation in a multi user setting

    There can be only one.


    • #3
      Re: Append operation in a multi user setting

      I've just been dealing with this in a different thread. I notice that the copy records operation doesn't mention that it locks the table. Would it be a better choice in a multi user setup?



      • #4
        Re: Append operation in a multi user setting

        I went through the various operations that A5 offers but couldn't find a way to solve my problem. The copy op won't do because 1) my target table has a fixed structure (always the same fields) for report generation purposes and you can't map fields between source and target 2) cannot do any calcs with fields, Append allows calc. The Append op. would have been perfect for my purpose.
        I am trying to append records on a invoice by invoice basis; ei when an invoice is created, parent record and child records are appended to target table when the invoice is saved. See attached representation. I have been working on this for a couple of weeks now and still at square one. Any help from A5 gurus would be highly appreciated.


        • #5
          Re: Append operation in a multi user setting

          The table should only be unavailable for a second or two. What about testing the table for it's lock status and if locked put up a message (to user2... user3 etc) that their update will occur in a moment... put them into a loop until the table is free and then update the table. The following code is from the help file and deals with a record lock. Because the whole table is locked I'm not sure how this would turn out but the idea is there. Unless you have a bucket of users just hammering the table with new invoices this scenario shouldn't really happen that often... don't you think?

          The only thing I'm not certain of in this code is... if you have an append process going... and you go after a record as below... will it return as locked?


          dim tbl as P
          tbl = table.current()
          status = tbl.is_record_locked()
          if (.not. status) then
          tbl.field1 = var1
          ui_msg_box("Error", "Record locked by another user")
          end if


          • #6
            Re: Append operation in a multi user setting

            Hi David:
            Thanks for shedding some light.
            Originally posted by Davidk View Post
            The table should only be unavailable for a second or two.
            In this case it is not as bad as I thought. In the help file it also says:
            " If any one else has the master table open, or if you open another form using the master table, the append will update the indexes after each record append. "
            I am not sure how to understand this. Does it mean that if A5 is in the midst of an appending op and gets a new request, it will process it for sure but after it has finished the current operation or does it just ignores the new request?

            Originally posted by Davidk View Post
            Unless you have a bucket of users just hammering the table with new invoices
            Unlikely; it's a network with 7 users. and they are not continuously entering records. I am just concerned about the case where the table is locked and a user tries to append records and it does not get appended because of this table locking thing. Then the reports based on the Merge table will be inaccurate.
            My major concern is to make absolutely sure that every invoice record is appended, otherwise reports will not be reliable.
            Last edited by gaby_h; 01-27-2009, 01:54 PM. Reason: make correction


            • #7
              Re: Append operation in a multi user setting

              from what it says... it will update the INDEXES after the append... not do the append... so... not sure about that one.

              I would test the table and if locked put up a busy message and loop until the table is free... the append from another user would only take a second... or less.


              • #8
                Re: Append operation in a multi user setting

                ok David, will do. Thanks for your help.


                • #9
                  Re: Append operation in a multi user setting

                  Hi Gaby,

                  The "Append" operation, and some of the other operations, have two modes of operation. If there is only one user (actually one session) using the table, it is operated in a batch mode where it does an initial query, locks the table, appends the data and then updates the indexes afterwards and releases the lock.

                  If more than 1 user or session exists, it runs the query, appends each record individually and updates the index entries for that record without a lock.

                  The 1st case is faster if appending a lot of records and the index rebuilding time is small. The 2nd way is faster if the opposite is true, plus doesn't lock the table.

                  To open a 2nd session of a table when you are on only one system, open a form of the table before starting the operation.

                  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


                  • #10
                    Re: Append operation in a multi user setting

                    Thank you Ira for your feedback, now I see how it works.