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
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

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 and Indexes

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    DBSUM and Indexes

    I am having a problem in v9 when using dbsum in an operation. In v9, the answer I always receive is 0, while in v8 I always get the correct totals for the same data.

    When I get the correct answer in v8 and then open in v9, I get the correct answer until I add a new record. I get 0 again until it is run in v8.

    To me it seems like an indexing problem. Anyone else notice this?
    Tags: None
    #2
    Re: DBSUM and Indexes

    I have attached a sample database backup to help clarify the problem.

    Open the only form and there is directions inside.
    If the need to reset the tables empty and pack only the ap_head and ap_Item tables.

    It works in v8 but there must be a bug in v9 that is stoping dbsum from working.

    If you need anymore information please reply.

    Comment

      #3
      Re: DBSUM and Indexes

      Jay,
      it appears to be an indexing update issue because when you perform the first step, leave the form which closes the table, updates the indexes, and return to the form, the second event works appropriately. Maybe you can get <index>.update() to work for you here.
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment

        #4
        Re: DBSUM and Indexes

        I tried the <index>.update() function and many others with no luck.

        As you mentioned, the only way it works in v9 right now is to close the form and reopen it.

        I hope the fix this bug in v9 in the next update becasue I have a feeling this may apply to other functions and operations also.

        Comment

          #5
          Re: DBSUM and Indexes

          Jay, if you have an example (and it sounds like you do) that works in A5v8 but NOT in A5v9 I recommend you submit a formal bug report. This message thread may or may not be referred to the bug review folks at Alpha. Use the Help menu in Alpha Five to send the bug report. Include the example and instructions to trigger the fault.

          Later ...

          On closer inspection I see that you use the field being populated in each append to define the value (using dbsum) that should be assigned to the same field. This seems circular to me. How about telling us, in words, what you're trying to accomplish? To me, it's asking for trouble to open, scan, sum, and close the master table in order to process a field in each record being "appended" TO the master table. Here you do it twice for each record being appended. So, in order to process a single transaction table record the append op must open the same table being appended to (the master table) twice, separate scans must be run, sums computed, and then both closed... for each record in the transaction table. Surely there has to be a better way.
          Last edited by Tom Cone Jr; 08-22-2008, 10:39 AM.

          Comment

            #6
            Re: DBSUM and Indexes

            The tables deal with purchase orders, received items and accounts payable.

            My requirements are to run the accounts payable off the purchase order numbers and bring in the line items of received goods that have not been invoiced for that particular po#. Also, if one received item was only partially invoiced, on the next invoice, only the remaining quantity to invoice should show. This should all be automated and require minimum input.


            I know this isn't the most efficient way. I am open to input on doing it better.

            Comment

              #7
              Re: DBSUM and Indexes

              Jay, I think we can help you but you need to slow down (at least for me!). Walk us through the sequence for a single complete transaction, including the partial invoice situation you describe. Use actual table and field names to explain the sequence as though we don't have a clue how you are doing business... cause we don't. I'm sure when you say "... run the accounts payable off the purchase order numbers..." that means something to you, but to a stranger it's greek. -- tom

              Comment

                #8
                Re: DBSUM and Indexes

                Sorry, I will try to be more descriptive.

                When you open the AP_Form (a set of ap_head and ap_item), the ap_no will auto increment and the date is defaulted to today. When you type the Po_no (This example is 200) and hit submit, an append operation will run and gather all the records in the rec_item table that have a PO number of 200. It will also check to see if the rec_item is already in the ap_item and the difference
                is greater than 0. If >0, then that data should be moved from the rec_item to the ap_item.
                The formula is:
                (rec_item:rec_Qty -(sum of all ap_item:Billed_qty with a po_no, part_no and rec_no all equal to this rec_item))

                That formula is also needed to calculate two fields in the ap_item.

                Basically, it comes down to: how do I calculate a sum of fields during an append to the same table in v9?

                I am trying to do this using a calculation rather than storing the data somewhere. It works in v8 just not v9.

                Comment

                  #9
                  Re: DBSUM and Indexes

                  I received feedback from Alpha confirming this problem.

                  The temporary workaround is to add this code in an operation after the dbsum() to force an index update.

                  ti = table.get("ap_item")
                  ti.update_production_index()


                  They will be fixing this problem in a future bug release.

                  Thanks to everyone who helped.

                  Comment

                  Previous template Next
                  Working...
                  X