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

Odd Auto Increment Issue

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

    Odd Auto Increment Issue

    I have a customer table that has a field named CustIDpk. It is a character field with a length of 6. I set it to Auto Increment with an initial value of "C1000" and all has been right with the world since 2008. I had assumed that I would have CXXXXX values, and the field would count from C1000 - C99999. I guess the assumption rule has bitten me, because as of yesterday we entered customer C10000, but he wasn't customer C10000, he was customer D1000. I have tried all that I can think of to fix it, including manually changing the values to C10000, C10001, etc... and redefining the default value to "C1000X". Every time it reverts to D1000 upon entering a new record. I just thought I would throw it out here to see what you all thought. Thanks!
    Tags: None
    #2
    Re: Odd Auto Increment Issue

    The autoincrement value never exceeds the length of the initial seed value when the character type is used. In your case C1000 will never increment the digits portion more than to 9999.

    You can turn off the autoincrement rule, make adjustments to the current values, and turn the autoincrement back on.
    There can be only one.

    Comment

      #3
      Re: Odd Auto Increment Issue

      That was my first try. I turned AI off, reset all of the new "D" values to make them in line numerically, changed the default value, turned AI back on, and D1000.

      Comment

        #4
        Re: Odd Auto Increment Issue

        I may have misunderstood. You reset all the current values to line up with what you originally wanted? IOW, inserted a "0" after every "C1" to increase the width. You deleted the D1000 record and packed the table?

        I don't use autoincrement so I may be missing something.

        I must be. C9999 should autoincrement to D0000, not D1000.
        There can be only one.

        Comment

          #5
          Re: Odd Auto Increment Issue

          Unfortunately character values do not sort as numeric so c9999 is the largest value in a character sort. Alpha will select the largest value to increment.

          Largest to smallest

          c9999
          c9998
          c9997
          c1002
          c1001
          c10002
          c10001
          c10000
          c1000
          c00002
          c00001

          Is how character values sort. You would need to write a custom increment function
          Last edited by Allen Klimeck; 05-07-2015, 01:30 PM.

          Comment

            #6
            Re: Odd Auto Increment Issue

            Thanks for that Allen.

            I think he can turn off the autoincrement, update the current field to

            c09999
            c09998
            c09997
            c01002
            c01001
            c01000

            turn it back on
            and the next value suggested should be c10000?

            that's if the field isn't used as a linking field anywhere.
            There can be only one.

            Comment

              #7
              Re: Odd Auto Increment Issue

              OK, Stan you are correct on two points. It did roll over to "D0000". If I insert after the c the Auto Increment does appear to start working again. It is a linking field, but I figure I can run the script on the other table as well and the link should remain.

              Comment

                #8
                Re: Odd Auto Increment Issue

                I figure I can run the script on the other table as well and the link should remain.
                Correct. You might consider moving to enough digits where you never have to encounter this again. No idea how long you've been running this application but what would two more zeroes hurt?
                There can be only one.

                Comment

                  #9
                  Re: Odd Auto Increment Issue

                  We're on the same page there Stan! Thanks Again for the help guys.

                  Comment

                    #10
                    Re: Odd Auto Increment Issue

                    Different page altogether: Use numeric 9 0 It always works and no problems with overages and I do use AI. Went to numeric many years ago.
                    Dave Mason
                    [email protected]
                    Skype is dave.mason46

                    Comment

                    Previous template Next
                    Working...
                    X