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

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

Custom Auto-Incrementing

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

  • Custom Auto-Incrementing

    Hi guys,

    I have a table which contains the following fields:

    Observation
    Detail
    Cause
    Product
    Obs_ID

    I'd like Obs_ID to be a unique# only when there is a combination of the first 4 fields.
    Therefore any record that shares the same Observation+Detail+Cause+Product will also share the same Obs_ID.

    Let me know if this doesn't make sense.

  • #2
    Re: Custom Auto-Incrementing

    I don't understand what your question has to do with auto-increment. It would seem to me you want Obs_ID to be a calculated field?
    There can be only one.

    Comment


    • #3
      Re: Custom Auto-Incrementing

      Hi Stan,
      Yes perhaps calculated field which increments to the next value for every unique combination.

      How about a unique index (Uniq_Obs) and using this calculated field rule:
      if(key_exist("Uniq_Obs",Obs_ID),previous("unq_obs","Obs_ID"),increment_value(previous("unq_obs","Obs_ID")))
      Last edited by hov333; 07-13-2017, 01:47 PM.

      Comment


      • #4
        Re: Custom Auto-Incrementing

        Thinking out loud here: what if there was another calc field that tested the 4 fields for content and was set to 1,2,3 or 4. Then your auto increment rule could be applied only if that number was less than 4? And instead of using previous() you could use tablemax() to get the last value for Obs_id and increment it.

        Edit: On 2nd thought scrap my first idea. Instead I have a question: if all 4 fields must match in order to share the same obs_id, why don't records that match on any combination of fields also share the same id? Thus only a non-matching new record needs to be tested for a new id? A keylink field that combines the data from all 4 fields would be one way. But some sample data would help...if the data in the fields is long, are there keywords that could be mined?
        Last edited by MoGrace; 07-13-2017, 03:55 PM.
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment


        • #5
          Re: Custom Auto-Incrementing

          I have no idea how this calculated field will perform with an increasing number of records.


          atest.zip
          There can be only one.

          Comment


          • #6
            Re: Custom Auto-Incrementing

            I spoke with John and we designed a system of a summary and append unique to control the ids by adding new combos to a master table and marking them as favorites as needed so the list is manageable.
            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

            http://www.iadn.com/images/media/iadn_member.png

            Comment


            • #7
              Re: Custom Auto-Incrementing

              there are only 120 possibilities of a 5 value combo provided no value is repeated, in other words, provided two fields cannot be of equal value (which I doubt they would in this case) so you cannot use an auto-increment field - you just need 120 different values, lol.
              If you do it would only auto increment 120 times then become obsolete as there are no more possibilites and any new value would be mean that two values share the same meaning.

              I just re-read your question and I made the mistake of counting the ID - 4 values would result in only 24 combinations so you just need 24 different ID's
              If you looked at it in terms of numbers that cannot be reused a 4 digit number can only be arranged in 24 combinations, on the other hand if there are infinate values in your 4 fields you would likely have no reason to create anything more than a GUID anyway as the number of combinations would be immeasurable.





              Last edited by CharlesParker; 07-14-2017, 01:33 AM.
              NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

              Comment


              • #8
                Re: Custom Auto-Incrementing

                Charles

                You are mis reading the premise.

                The fields are not numeric.

                We have a working solution as I stated.
                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

                http://www.iadn.com/images/media/iadn_member.png

                Comment


                • #9
                  Re: Custom Auto-Incrementing

                  I'd like Obs_ID to be a unique# only when there is a combination of the first 4 fields.
                  Therefore any record that shares the same Observation+Detail+Cause+Product will also share the same Obs_ID.
                  I' m sorry to chime in here with this radical statement but if you read these two lines the results are not a unique value.
                  Is the intent to have a field value that groups record based on a value or trying to truly giving a record a truly unique value?
                  Mike W
                  __________________________
                  "I rebel in at least small things to express to the world that I have not completely surrendered"

                  Comment

                  Working...
                  X