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

Conditional Auto Increment?

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

    Conditional Auto Increment?

    Is there a way to have a numeric field set to auto increment conditionally? Example - when entering a record, if the value of field 1="Red" then field 2 would be left blank. However, if the value of field 1="Blue" then field 2 would be able to find the last record that was not blank and increase it by one.
    Thanks
    Tony

    #2
    RE: Conditional Auto Increment?

    Tony, what you are implying is that "1=red" is simply invalid in which case you could limit field input using a validity field rule. Using the validity test you could switch to another input table if input=1 (which makes little sense from a design perspective). Other than that there is no point in not incrementing records per each entry as any action performed on blue or red or any other color could filter based on the field value.

    If not than what do you intend to do with the non incremented records, by design if the record is accepted it must incrementally add to the database or be discarded.

    What exactly are you trying to do? Please give more detail.

    Marc
    Marc King
    A5solutions

    Comment


      #3
      RE: Conditional Auto Increment?

      Marc
      The reason for not wanting to increment some of the records is that when we input a inventory item we also put a metal tag on that physical item that has a number stamped on it that is the same as the alpha five number.

      I am also wanting to keep up with another type of inventory that does not actually require a metal tag. Just trying to keep from wasting about 10000 metal tags per year.

      I need to be able to see both types of inventory in the same browse.

      Hope this clears up question
      Thanks
      Tony

      Comment


        #4
        RE: Conditional Auto Increment?

        Tony,

        So... why not add a small logical field, 'Metal_tag', and set it's value yes or no during data entry. The logical flag could be used to produce your list of metal tags to print.

        -- tom

        Comment


          #5
          RE: Conditional Auto Increment?

          Yes, Tom is correct, adding a logical metal_tag field and a calculated tag_number field is where I would start. Your calc field script would need to then:

          set a starting value
          if metal_tag = .T.
          find last tag_number
          +1 set field (tag_number)
          else tag_number = ""


          Perhaps someone has time to put an example together.

          Marc
          Marc King
          A5solutions

          Comment


            #6
            RE: Conditional Auto Increment?

            Hi Tony,

            >>Just trying to keep from wasting about 10000 metal tags per year.

            Comment


              #7
              RE: Conditional Auto Increment?

              Thanks for the ideas

              Reading some of the old threads, would this work for the field rule of field_1?

              if(field_1="blue",increment_value(field_1),0)

              The way I understand the increment _value function, it looks for the highest value or am I mistaken.

              Thanks
              Tony

              Comment


                #8
                RE: Conditional Auto Increment?

                Tony,

                I would create a start table for the application (with only one record in it) and have a character field to hold the current highest incremented number. If you want a record to have an incremented number in a field, go to the start table, grab the character string, convert the string to a number, add one to it, convert it back to a character string and stuff that string into the record as well as back into the start table.

                I always use a start table and base the main menu on it.

                Hope this helps,

                Regards,
                Jay Talbott
                Jay Talbott
                Lexington, KY

                Comment

                Working...
                X