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 on an optimized system

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Auto-increment on an optimized system

    I have approximately 10 users set up with our database optimized(soon to be 20 users). Last week, two users were entering a new record at the same time. Each record gets identified with an autoincrement number. What happened was that they both ended up getting the same number. Is this because since all the files are copied down to each user's machine, the field rules; particularly autoincrement, don't act the same way as they would if the users are going directly at the database on non-optimized machines sharing the same field rules as opposed to having their own? I like the optimize feature but can't really continue with it if this occurs more frequently.
    Tags: None
    #2
    RE: Auto-increment on an optimized system

    Dave,


    I believe that if I credit Tom Cone for the following, it will not be considered plagiarism (grin).




    Tom recently wrote:


    One idea that works well in some apps is to begin the new record with a button push. The button's OnPush event script can begin the new record, and then save it immediately. This captures the autoincrement field value and prepares the table for the next workstation's new record, too. Edits occur after the record is saved, so to speak. The only drawback here is that if the original new record needs to be cancelled, you don't get the autoincrement value back to re-use after you delete the unneeded (partially complete) record. In many cases this is a matter of little consequence.




    I hope this helps.


    Regards,

    Jay Talbott
    Jay Talbott
    Lexington, KY

    Comment

      #3
      RE: Auto-increment on an optimized system

      Dave,

      Also not wanting to plagiarize :-) I found a solution given by Cal Locklin especially useful. See: http://www.aimsdc.net/Tips_Funcs/Auto_incr_c.htm

      It takes into count all vagaries of networked multi user concurrent operation. Works like a charm - Thanks Cal!

      HTH

      Charles
      SwissCharles
      Between the Alps and a comfy place

      Comment

        #4
        RE: Auto-increment on an optimized system

        Thanks for your replies. My question is though, since I have all my users in an optimized environment, does it behave differently than if everyone was going directly at the server?

        Comment

          #5
          RE: Auto-increment on an optimized system

          Dave,

          Short answer, No.

          -- tom

          Comment

            #6
            RE: Auto-increment on an optimized system

            The autoincrement number is not fully assigned until the record is saved. Therefore 2 users can temporarily be looking at the same autoincrement number. The first user to save will get that number. The second user will see their number change once the save occurs. That is the normal operation of the autoincrement field, and it doesn't matter whether the database is network optimized or not. If you find 2 records with the same value in an autoincrement field in a table, then you have discovered some bug in A5v5.

            Comment

            Previous template Next
            Working...
            X