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



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 Help Please

  • Filter
  • Time
  • Show
Clear All
new posts

    Auto Increment Help Please

    Hey Guys... New guy here. I am building a database to track the progression of chemical mixtures. In my mixture table I have a Mixture field and a Version field.

    In my form I have a browse that shows the mixture name and version number. There is a version number because a "Master Mixture" may require several alterations before it is perfected. I would like a chemist to be able to highlight the record that needs to be remixed and then click a button to open the selected record for editing but have the version number do an auto increment for a mixture with the same name (curent record). When the button is clicked, whether it is on the 3rd version or the 1st, it should automatically update to the next highest version associated with that mixture name field.

    How do I make this happen? Please help, I'm stuck!

    Re: Auto Increment Help Please

    Are you keeping a history of the versions...the way you describe the sequence you are not as when a record is simply edited, you no longer will have any history. Answering this will help to give a more specific answer. Otherwise, all you would need is to add whatever you want to your version field's value in the OnChange of a field you decide upon to be one that requires a version update.

    And Welcome to the messageboard!!....we try to answer all questions but some fall by the wayside if not enough info is given for a guess to be will find that many questions are answered very quickly if a sample is given (I don't believe a sample is warranted in this case, but could be dependent upon level of expertise and understanding by you and us).
    Last edited by MikeC; 05-31-2009, 02:12 AM.
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau


      Re: Auto Increment Help Please

      Hey Mike... I want there to be a record of every version created. The name of the mixture will always stay the same but the version number will change every time a new version is created. Hope this helps. Thanks.


        Re: Auto Increment Help Please

        Joe, you won't be able to use the auto-increment field rule for this. It produces a single sorted list of field values, and increments the highest value it finds when the new record is saved. You want separate sorted lists for each possible "mixture", incrementing the highest version value found for each particular mixture when the record is saved. You're going to have to do some custom scripting to achieve this.

        If it were me I'd use two table fields. One for the mixture, one for the version. I'd index both fields. I'd also index the concatenated combination of these fields. These would probably be stored in a separate supporting table to expedite the computation. When computing the next "version" for a given mixture I'd probably use a custom UserDefinedFunction (UDF).

        In pseudocode this function would:

        Open the table of mixtures/versions

        Set the index to the concatenated

        Fetch_find the first mixture

        Step through the records until you get to the last version

        Capture and increment that version value

        Enter a new mixture/version record with an incremented field value

        close the supporting table

        Increment the captured value and use it in the new record being entered in the main table.

        NOTE: An even faster approach would store only the "last" mixture/version record in the supporting table. the UDF would fetch the mixture in the supporting table, increment the version, save it, and use the incremented version value in the main table.