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

Error when trying to display a Report

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

    Error when trying to display a Report

    When I attempt to preview an Invoice for print, A5 sends an error message. It seems this is due to filtered indexes that A5 creates. Is it a bug and what's the workaround?
    Open SalesForm, see the note.
    Tags: None
    #2
    Re: Error when trying to display a Report

    Gaby,

    I just found an error on your "customer_id" setting.

    I revised the "customer_id" in the fieldRules with Table lookup and changed in the form. It works fine.
    see attached zip files.

    Comment

      #3
      Re: Error when trying to display a Report

      Hi John:
      Thanks for coming to the rescue. So the trick was to delink Customer table from Sales table in the set and use LU function to show customer name. I would have never thought of that. Thanks.
      Still don't see why an error message pops up when the customer table is linked to Sales table.

      Comment

        #4
        Re: Error when trying to display a Report

        Gaby,

        I think your Event Script cause this problem.

        I just added new customer table and join(set) here and it works fine.

        Why don't you add new Customer table and try before touch your Even Scripts in your Customer table.

        Comment

          #5
          Re: Error when trying to display a Report

          Gaby, I'd argue that you don't want to filter the customer lookup list in the first place. Otherwise you can't record a prepayment.

          An alternative that might help would be to add a field to the customer table, logical, and set it true whenever a transaction creates a balance, then set it false when the balance is returned to zero. Filter the lookup on the logical field.

          Yet another approach would be to use a post field rule in the transactions table to add transaction amounts (plus and minus) to a running balance field in the customer record. The payments table lookup field rule could be filtered to show only non-zero field values.

          I think your original problem is not so much that you were using a filtered lookup to populate payment table records, causing Alpha Five to create a special index. I think the problem was with the expression used to filter your Customer table records. You used dbsum() to compute each customer's current balance, and then excluse the zero balance customers from the lookup. Dbsum() must open the table, search, sum, and close the table each time it's evaluated. When you use it in a field rule like this it must be done once for each record in the table, just in order to create the filtered index. The result is lots and lots of disk activity that does not get fully processed by the timne the report preview is loaded. I do not think you'll have a timing problem with a simple filter. I'm not surprised you had a problem when you use dbsum() in the filter expression.
          Last edited by Tom Cone Jr; 12-14-2009, 09:44 PM.

          Comment

            #6
            Re: Error when trying to display a Report

            I guess John's solution is ok for this pilot project (it's for a friend, single user and not transac intensive).
            However I do need to rethink my approach in light of Tom's suggestions. I like the posting approach but insure how to implement it. Sum of LineItems in invoicedetail get "posted" to InvoiceHeader by Set Field script. Same with Sum of LineItems in Paymtdetails that gets "posted" to PaymtHeader. Now How can i post these 2 aggregate amounts to Customers table? Field Rules trigger when there is manual input by the user; InvoiceHeader and PaymtHeader are populate by Set Field script.

            Comment

              #7
              Re: Error when trying to display a Report

              Gaby
              Code:
              Sum of LineItems in invoicedetail get "posted" to InvoiceHeader
              Check here - Child Total in Header Table: http://msgboard.alphasoftware.com/al...ad.php?t=82883.

              Comment

                #8
                Re: Error when trying to display a Report

                Just a point that has been made many a time here on the messageboard.....many timing issues can be eliminated if a UDF is used instead of script.

                The result is lots and lots of disk activity that does not get fully processed by the timne the report preview is loaded.
                So whatever needs to be accomplished before the report preview is called could be placed into a UDF---that way everything within the UDF will finish before the calling of the report preview.....
                Mike
                __________________________________________
                It is only when we forget all our learning that we begin to know.
                It's not what you look at that matters, it's what you see.
                Henry David Thoreau
                __________________________________________



                Comment

                  #9
                  Re: Error when trying to display a Report

                  Hi Mike:
                  I have never used a UDF before, but will definitely take this opportunity to find more about it and how to use it in this case. Thanks for pointing this out.

                  Comment

                    #10
                    Re: Error when trying to display a Report

                    Gaby,
                    Here is how....actually very simple. Copy the xbasic that comprises your script---make sure any variables needed are dimmed within the script(if not global/shared and if needed outside of the function to make them global/shared (not sure if shared will do it but easy to know if it isn't with the errors that will come up!!).

                    Go to the code tab of the control panel, choose the New button on the control panel...choose Function. Type in a name for your function and press the OK button. Between the Function and End Function that appears, Paste your xbasic code. To use the function just call it as you would an Alpha function.
                    Mike
                    __________________________________________
                    It is only when we forget all our learning that we begin to know.
                    It's not what you look at that matters, it's what you see.
                    Henry David Thoreau
                    __________________________________________



                    Comment

                    Previous template Next
                    Working...
                    X