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

Sort by Calculated Field

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    RE: Sort by Calculated Field


    Did you try running a report with the calculated balance?

    If you do, and that works, then filter the report so that only the balances 0 show.


    Jay Talbott
    Jay Talbott
    Lexington, KY


    • #17
      RE: Sort by Calculated Field

      Doug Barr:

      For all it's worth, I'm testing my own application and form for a similar query on an 'enabled' calculated form field with identical behavior as your's in Query by form..... 'Invalid Expression'


      Like the others, I've a bunch of field rule posts to a running balance field in the master upon which I can filter that information in reports and views.



      • #18
        RE: Sort by Calculated Field


        Minor point first. The initially disabled fields were not included in the form's tab order. You can include them by checking the "tab" box in the field's properties. You can edit its position in the form's tab order as you would any other field (view/set tab order).

        Are the calc fields defined in the form or in the table? It may be that QBF is supported for one but not the other.

        Unfortunately, I am not in a position to test this out at the moment.

        Bill Hanigsberg


        • #19
          RE: Sort by Calculated Field

          Hi again,

          Check this out:
          Msg ID: 37077
          Subject: RE: query by form Ver. 4.5
          Author: Selwyn Rabins
          Date: 03-12-2001 21:21

          a5 CAN do qbf on your calc fields.

          however, a calc field that you define at the form level, by default, has its "disabled" property turned on.

          you just need to go to the calc field on the form in design mode, right click. so to field properties. setup tab. uncheck "disabled".

          then you will be able to do qbf on this field.

          I used the search feature to find this thread. It is worth reading in full.

          To my surprise I discovered that I contributed a demo on running QBF on calculated fields. Didn't remember that!

          I should also remember the search feature. We're reinventing the wheel here.

          Bill Hanigsberg


          • #20
            RE: Sort by Calculated Field

            This is interesting.

            I decided to check a form that I've been working on. I two calculated display fields on my form, I've unchecked the disalbe switch on both of them.

            SUBTOTAL get's it's calculated value by a total() function.
            OLDSUBTOT get's it's calculated value by dbsum() function.

            Both operate correctly and return the same exact value for each record. However, I can only do a query on OLDSUBTOT, and "not" SUBTOTAL.

            Attempting a query on SUBTOTAL {field using total()} returns the same warning you guys are getting.


            Thank you,
            Mike Konoff


            • #21
              RE: Sort by Calculated Field

              Mike, I think you're on to something useful here.

              I remember bumping into limitations of total() before. Have found it most useful in the context of a report... not in the context of a form...

              Using dbsum() instead I have built a simple example illustrating how a current balance might be displayed on a form...

              Unzip the attachment to a separate folder. Do not mix it with your development work.

              The design of the calc fields is explained in 'DesignNotes', which you can reach from the startup form.

              -- tom


              • #22
                RE: Sort by Calculated Field

                Mike, here's an improved illustration. Two forms are now included.

                OrdHist1 uses embedded browses for the child tables.

                OrdHist2 illustrates how one might do this using a tabbed subform.

                -- tom