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

Max Value

  • Filter
  • Time
  • Show
Clear All
new posts

  • Max Value


    I'd like to set a calculate field that retrieves the largest value of all records stored in one particular field.

    DBMAX is close, but it searches for records that match a key value and returns the highest value of a return_field.

    I'd like to return the greatest or highest value of a field from all records.

    Is this possible?

    Thank you,
    Thank you,
    Mike Konoff

  • #2
    RE: Max Value

    Looks like tablemax() will do it, provided you use a filter of .t.

    -- tom


    • #3
      RE: Max Value

      Thanks Tom...I'll check it out.

      Thank you,
      Mike Konoff


      • #4
        RE: Max Value


        It works. Thanks for your help.

        Thank you,
        Mike Konoff


        • #5
          RE: Max Value

          Other than setting a field to AutoIncement, this seems like a slick little tool to make a home made autoincrement such as tablemax()+1.

          Anybody know any reason why this might not be a good way to go?

          Thank you,
          Mike Konoff


          • #6
            RE: Max Value

            When you do a table function, Alpha probably has to do a fetch on all records and may not necessarily take advantage of indexes. Let's say you have an index tag that is a a relative record number. Doing a lookupc("L" and adding one to the retrieved number seems like a much better way of doing it. Even this will have problems when simultaneous users are on the system, which is why I always use a function that retrievss the last number from a special table.


            • #7
              RE: Max Value


              It sounds to me that you do autoincrementing with something other than A5's "autoincrement" field rule. True?

              For some reason, and I don't recall why, it seems to me that A5's built in autoincrement routine is not as foolproof as A4's. Is this what you find?

              Thank you,
              Thank you,
              Mike Konoff


              • #8
                RE: Max Value


                Like John and others, I store the last record value in a field in a dummy table and use this to increment to the next available record ID. If I need to verify that the number stored is correct, or to reset it due to an error, I use tablemax() to find the last value in the field.

                There are a couple reasons for using this method over autoincrement. I still use autoincrement if the value is not displayed or has not particular relavance other than a backgroud ID. But there are cases where autoincrement does quite work the way I would like.

                1. One case can be if the ID is a combination of two values. One user wanted the year as the first four digits of an ID combined with an incremented numeric value added (20010980, 20010981, 20020001, 20020002, etc) This required some calculation of the ID which isn't possible with autoincrement.

                2. Another case occurs where you don't want gaps in the ID, such as in invoice numbers. If the number is autoincremented and the record is deleted, that number won't be used again. There are a number of stategies to combat this one using the OnDeleteRecord event.

                3. If you have multiple users on a network, you may want to fix the ID number at some point in the record entry for some other activity or calculation. If two people are entering records in the table at the same time, the autoincrement value is assigned at save, so whoever saves first gets that number. Using your own increment allows you to open the dummy table, either at the CanSaveRecord event or the OnEnterRecord event in field rules, get the last record used, increment that, save the new value back to the dummy. Now you have your number and it won't change and the next user will get a new, fixed, incremented number when they hit that event.