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

Calculation BUG!!!

  • Filter
  • Time
  • Show
Clear All
new posts

  • Calculation BUG!!!

    I have a database table that has about 600,000 records. I have 12 fields that are numeric with no decimal places that represent the 12 months in a year. I have a 13th field that hase a field rule that calculates a total for the 12 months by simply adding the 12 fields together for a total.
    I found that the calcul;ated total is off by 1 in either direction. I've run an operation calculating the total and get the same results. I then went into Alpha4V6 and performed the same calculation on the table and it worked perfectly. I've also done this with MS Acces and foxpro and get a correct result. I've attached screen shots showing the problem before recalculating with Alpha4.

  • #2
    RE: Calculation BUG!!!

    I SERIOUSLY doubt that there is a bug in a5 calculations.

    Of course you can prove me wrong by attaching a table with a few records (don't want to get 600,000 records) that shows the problem.

    If i am wrong, i will wipe the egg of my face and we will fix it.


    • #3
      RE: Calculation BUG!!!

      I'll clean the problem table down to a few records. Thats the problem. All of the tables that I've built dont seem to have this problem but, I have never had a table with this many records. Could the problem be be withn the size of the file?


      • #4
        RE: Calculation BUG!!!

        Have you tried setting up your calc using the round() function? Round to zero decimal points and see what you get.

        - Steve


        • #5
          RE: Calculation BUG!!!

          Fred, might this be a display update issue? If you move to a different row, and then back again does the right value show up?

          Is this a field rule calc field, or is it defined at the form level?

          The size of the table is probably a matter of no consequence. If I understand correctly you're not summing a series of records, but a series of fields in one record, right ?

          -- tom


          • #6
            RE: Calculation BUG!!!

            Thats right Tom, it is simply adding or summing up 12 numeric fields that have no decimal places. I'm woundering if it could be a problem with the speed of the calculation process. It worked perfectly with Alpha4V6 which churns thru the file slower than Alpha 5. When I ran the global update with A4v6 it calculated every field correctly. But I ran the operation in A5V5 as well as reevaluate field rules and operations with the incorrect results. It seems to miss the calculation randomly threu the table. I've tried again this morning and had the same results.


            • #7
              RE: Calculation BUG!!!

              I'll try that method today. The calculated field is simply summing up 12 numeric fields that have no decimal places. I have not had this problem with smaler tables in the 175,000 record range. I'm running Win XP on a 2.53ghz intell with a 200 gig HD.


              • #8
                RE: Calculation BUG!!!


                Try turning off the field rule. Make the field 'user entered' as far as field rules are concerned. Then run your global update operation again.

                -- tom


                • #9
                  RE: Calculation BUG!!!

                  Thanks Tom, I'll try that.


                  • #10
                    RE: Calculation BUG!!!

                    why don't you attach a file that show the problem?