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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Auto-Increment value duplicated in multi-user environment

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Auto-Increment value duplicated in multi-user environment

    The biggest problem with the autoincrement field rule is that the value displayed in the field upon starting an enter may not be the same value as when the record is saved.
    Let's say user one starts an enter and the field displays a value of "100".User one is very slow and does not sve the record for some time.When use two starts an enter he also gets the value of "100 in the field.Usertwo saves the record before user one.When user one saves the record, the value in the field will be "101".If the program adds any auxilliary records prior to committing the record, the auxilliary records will be messed up.

    Comment

      #17
      Re: Auto-Increment value duplicated in multi-user environment

      If the program adds any auxilliary records prior to committing the record, the auxilliary records will be messed up.

      John,
      That is a very good point.
      I never allow adding/editing a child record until the parent is saved.

      Comment

        #18
        Re: Auto-Increment value duplicated in multi-user environment

        Great discussion guys! Finnian was right ... coding error.

        Comment

          #19
          Re: Auto-Increment value duplicated in multi-user environment

          Originally posted by martinwcole View Post
          Yes, Peter, I agree.

          Interesting: I just now realized that the hosptial is running a WAN - i.e., the app is shadowed, but to a server in a different city, and it is actually running!!! Wonder what kind of broadband they have - must be really bad#$@!!!!

          I had always heard to never try to use a shadowed app over a WAN.
          impressive apps you build my compliments but using DBF tables on a medical apps has risks.
          your apps is more save on security, performance and DB transactions using a [remote] SQL backend

          Comment

            #20
            Re: Auto-Increment value duplicated in multi-user environment

            I agree, but they started in V5 (and even then I moved them form Alpha Dos V4) back in 2003. The data is scrambled/encrypted and is quite secure, and passes all current HIPPA requirements - although that is subject to change in the future.
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment

              #21
              Re: Auto-Increment value duplicated in multi-user environment

              I use the ai daily with up to 50 people inputting. Never an issue. I do one thing I did not see here.

              On entering a new record, the ai is done and record save immediately. The the user can then put in what they need to.

              Maybe that will help??


              .
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment

                #22
                Re: Auto-Increment value duplicated in multi-user environment

                Hi All,

                Older 4.5 versions of Alpha auto increment would always leave a gap in the ai field number if a record was deleted.

                e.g. add new record 101 then delete the record then add new record the new number would be 102 and 101 slot cannot be applied again, current versions of Alpha will result in another 101 number. So if any child records have been added before the delete then big problem, they will be attached to the wrong parent.

                This is OK if you cascade deletes in a set but sometimes the child record must never cascade or be removed.

                I always prevent the deletion of a parent if there is no higher ai field value already in the table.

                Michael

                Comment

                  #23
                  Re: Auto-Increment value duplicated in multi-user environment

                  Originally posted by JohnZaleski View Post
                  The biggest problem with the autoincrement field rule is that the value displayed in the field upon starting an enter may not be the same value as when the record is saved.
                  Let's say user one starts an enter and the field displays a value of "100".User one is very slow and does not sve the record for some time.When use two starts an enter he also gets the value of "100 in the field.Usertwo saves the record before user one.When user one saves the record, the value in the field will be "101".If the program adds any auxilliary records prior to committing the record, the auxilliary records will be messed up.
                  And sometimes it isn't actually messed up - it just looks messed up.

                  Since both users start out with "100", when either user saves the parent and starts adding child records, those child records may show up on the other user's system. Once that second person saves his parent record, those child records should disappear - in the meantime, user 2 has already panicked.

                  So, if you force all users to immediately save the parent record, the whole problem goes away and the standard autoincrement works fine. BUUUT, there's a catch - now the user can't simply cancel the parent record when they realize they didn't actually want to start another record. You could create a 'delete' routine but (a) that adds complexity and (b) there may be a problem with packing it on a networked system.

                  I haven't checked but I'll assume Mr. Humby is correct and the latest versions of A5 will now re-use that deleted ai number even though it is simply deleted and not packed yet. This is different than previous versions and actually makes this a potentially viable alternative IF you never undelete records.

                  Comment

                  Previous 1 2 template Next
                  Working...
                  X