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

DBSUM problem

  • Filter
  • Time
  • Show
Clear All
new posts

    DBSUM problem

    Here is my problem:

    (Relavent fields only)

    Parent table: INVOICE
    Fields: Transaction (sequential)
    Amount (n 12.2) Total Inv amt

    Child table: CHARGE
    Fields: Transaction (link with Invoice)
    Amount (n 12.2)

    Formula for new variable to make sure individual charges
    total the invoice amount:

    Above does not work. It returns a character, not numeric,
    The same formula has been used before and it works OK,
    but not this time.

    Any suggestions?

    RE: DBSUM problem

    i don't know why this is happening to you.

    i just confirmed that dbsum() returns a numeric by typing this in the interactive window:

    ?dbsum("invoice_items","invoice_number", "000001", "quantity")
    = 79.000000


      RE: DBSUM problem

      Would it help to change your DBSUM to the following...


      Thank you,
      Mike Konoff


        RE: DBSUM problem

        Yes, that is how it works in my other applications.
        Somehow, this one does not want to return a numeric expression.
        I thought it was because I upgraded my A5 version, but went back
        to older applications and it still works with those databases.
        I even tried VAL(DBSUM(....etc. but that does not work either.
        I also tried 1 * dbsum( ... etc to force a numeric field, but no
        Can I send you a zip file with the two tables to see if you can
        figure it out? There's got to be a reason.



          RE: DBSUM problem

          Yes, I tried using the val() formula but that did not work.
          I also tried 1 * dbsum(... etc) to see if that forces a numeric



            RE: DBSUM problem

            please don't send me anything directly.

            rather attach a file to a message on the message board.

            first, refer to the message in the "Announcements" section for information on how to send the minimum number of files.


              RE: DBSUM problem

              I'm glad I asked!

              This new message board is great! This is just another reason
              why A5 is so great!



                RE: DBSUM problem

                Finally figured it out.... but sounds like an A5 problem. Is it?
                Using the interactive window I made a typo error and that's how I figured it out.

                This did not work:
                returned a "no data" message

                This worked:

                Note the "transactio" for the field name does not have an "N" at then end.
                Thus, I assume field lengths cannot be longer than 10 characters unless separated by an "_". Again, I assume "trans_action" would have worked.
                Is this correct?



                  RE: DBSUM problem

                  I have occasionally had index and field names truncate to 10 characters. I have never been able to pin this on a specific cause but I suspect crashes and heavy development without frequent db compacts.

                  I conclude that conservative practice is to use short names. I usually manage to make myself follow this rule. Whenever I notice that a name has shortened I adjust the code to the new name rather than restoring the old name.

                  Bill Hanigsberg


                    RE: DBSUM problem

                    Thanks very much for confirming the nature of my problems.
                    I'll know better in the future.



                      RE: DBSUM problem

                      Hi Bill:

                      Here's one guaranteed way to force truncation of long field names. Someone needs to move data from one location to another and copies over just the dbf/fpt files. Then the user opens that table with A5 without the original data dictionary present. If no data dictionary at all is present, all long names will be truncated when A5 creates the new one. If an outdated dd is present which doesn't contain LFN info for all the fields, then any new LFN that has been added will likely be truncated.

                      I've never (so far) had a long field name truncate other than for one of these reasons. For this reason I rarely just copy dbf's. I almost always reconfigure/zap/append.