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

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

  • #16
    Re: auto increment

    Originally posted by civitas View Post
    Thanks so much! I really appreciate the help. -- Arthur
    Please describe what you found so anyone who visits this post later might also be able to diagnose their issues.
    There can be only one.

    Comment


    • #17
      Re: auto increment

      Originally posted by Stan Mathews View Post
      You don't. Temporarily remove the auto-increment designation, populate the field via an update operation, then reinstate the rule. The auto-increment is a data entry field rule, not something that can be applied retroactively to existing records.
      I'm trying to move an A4v8 "client" file to A5v8. It has an ID field of 5 characters, the max value of which is 26670. No matter what I do, the value entered is 99000. I tried this suggestion of first removing the auto-increment designation and doing an update. Didn't work. I then manually entered three records with values 30000, 30001, and 30002, then re-established the auto-increment. That didn't make any difference either. Still enters 99000,

      I played with it a bit. Made the field 6 characters instead of 5, for example. Then the auto-increment entered the value 990000.

      Very frustrating. This file is way too big to lose. I need some major help here, please.

      Comment


      • #18
        Re: auto increment

        I've only seen this when my ID field had unexpected data in it. If it were me, I'd study the table to verify that the highest field value is only "26670".

        It's not clear from your post if the field is numeric or character type. If you can't solve this on your own, let us know which is applicable when you reply.

        -- tom

        Comment


        • #19
          Re: auto increment

          Richard

          Open a default browse for the table. Highlight the ID field, then from the menus - navigate - tools - field statistics. You should see something similar to what the attached image shows for Alphasports.

          Check the max value for that field.
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          Comment


          • #20
            Re: auto increment

            Originally posted by Tom Cone Jr View Post
            I've only seen this when my ID field had unexpected data in it. If it were me, I'd study the table to verify that the highest field value is only "26670".

            It's not clear from your post if the field is numeric or character type. If you can't solve this on your own, let us know which is applicable when you reply.

            -- tom
            Interesting. It's a character field in both A4 and A5. When I sort that field in A4 it displays in strict numerical order--first record "1", last record "26670". When I sort the same field in A5 it shows the first or lowest record as "1", but the highest is "99". Because of some deleted records over the years, there is no record "999" and also there is no "9999". Apparently, the decimal placeholders, or zeros, didn't come thru the conversion properly. Record "00099" in A4 came through as "99000" in A5.

            How can I keep the zeros in their proper places?

            Comment


            • #21
              Re: auto increment

              Richard, what you describe suggests to me that the data type for the ID field in Alpha Four was numeric, and Alpha Five converted it to character. Did you append records from the Alpha four table, or did you just begin using a copy of the A4 dbf?

              In any case the answer to your original question is now clear. The "99 " sorts to the top of the list, and is being used by the autoinc field rule as expected.

              If you turn off the field rule you can define an "update" operation that will prepend leading zeros using an expression like this:

              padl(alltrim(ID), len(ID), "0")

              I caution you not to do this without making a safety backup copy of your data first. Many an update operation has gone awry and they're dang difficult to reverse. Run the update against a throw away copy of the table first, before running it against your real data.

              Once the field values have been zero filled you can then turn the autoinc field rule back on.

              Comment


              • #22
                Re: auto increment

                Originally posted by Tom Cone Jr View Post
                Richard, what you describe suggests to me that the data type for the ID field in Alpha Four was numeric, and Alpha Five converted it to character. Did you append records from the Alpha four table, or did you just begin using a copy of the A4 dbf?

                In any case the answer to your original question is now clear. The "99 " sorts to the top of the list, and is being used by the autoinc field rule as expected.

                If you turn off the field rule you can define an "update" operation that will prepend leading zeros using an expression like this:

                padl(alltrim(ID), len(ID), "0")
                Yes, this sounds right to me. Can you give me a little more detail about preparing the update? The genie doesn't seem to allow what I need to do.

                Comment


                • #23
                  Re: auto increment

                  OK, got it! Had to mess around with the indexes and not use the genie, but it worked! Thanks for everything.

                  Richard

                  Comment

                  Working...
                  X