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

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

Summary Operation - Unhandled Exception

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Summary Operation - Unhandled Exception

    Snippet of code here from a summary operation. Generates an unhandled exception when I try Field20. It's a character field, it's spelled correctly. Anyone know why?

    Code:
    . . .
    sum.field18 = "YEAR"
    sum.code18 = 6
    sum.field19 = "INVNO"
    sum.code19 = 6
    sum.field20 = "Svc"
    sum.code20 = 6
    sum.field21 = "POS"
    sum.code21 = 6
    . . .
    -Steve
    sigpic

  • #2
    Re: Summary Operation - Unhandled Exception

    Works here with that field name in V8.

    See if it runs for you on my sample table.
    There can be only one.

    Comment


    • #3
      Re: Summary Operation - Unhandled Exception

      Not that simple Stan.

      And even if it was, it doesn't tell me why I get the error in V10.
      -Steve
      sigpic

      Comment


      • #4
        Re: Summary Operation - Unhandled Exception

        Just trying to see if the svc field name triggered the issue. I don't have V10 so I couldn't test anything similar to what you might be using.
        There can be only one.

        Comment


        • #5
          Re: Summary Operation - Unhandled Exception

          I can't change that field. It's in a complex system built by someone else I'm now supporting.
          -Steve
          sigpic

          Comment


          • #6
            Re: Summary Operation - Unhandled Exception

            Just tried creating a table so that I could test the svc field in the 20th position and it ran ok.

            Code:
            sum.field18 = "Q"
            sum.code18 = 6
            sum.field19 = "R"
            sum.code19 = 6
            sum.field20 = "Svc"
            sum.code20 = 6
            sum.field21 = "S"
            sum.code21 = 6
            You have examined the data in the svc field for "strangeness"?
            There can be only one.

            Comment


            • #7
              Re: Summary Operation - Unhandled Exception

              Hi Steve,

              What's the field type? What is it's value in the 1st record's data

              Is it the fact that it is the 20th summary field. Reduce the number and see if the field still has an issue.
              Regards,

              Ira J. Perlow
              Computer Systems Design


              CSDA A5 Products
              New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
              CSDA Barcode Functions

              CSDA Code Utility
              CSDA Screen Capture


              Comment


              • #8
                Re: Summary Operation - Unhandled Exception

                Well this is a revolting development.

                I changed the code to below and still got an unhandled exception. Basically did field INVNO twice.

                Code:
                . . .
                sum.field18 = "YEAR"
                sum.code18 = 6
                sum.field19 = "INVNO"
                sum.code19 = 6
                sum.field20 = "INVNO"
                sum.code20 = 6
                sum.field21 = "POS"
                sum.code21 = 6
                . . .
                Ira - Character type, can't find anything unusual. But it's not even executing the tbl.summarize() because of the error.

                More: I changed SVC to the 19th position, and limited the summary field count to 19. Again, unhandled exception.
                -Steve
                sigpic

                Comment


                • #9
                  Re: Summary Operation - Unhandled Exception

                  Hi Steve,

                  Try it with just a couple of fields. Then change a few of the fields to the problem fields. Just keep the total fields small. Try a different summary type.

                  And in a few weird cases there is an unseen non-displayable character embedded into a line. I've seen that on rare occasions. Deleting the line and lines around it made it go away. Or start it from scratch.
                  Regards,

                  Ira J. Perlow
                  Computer Systems Design


                  CSDA A5 Products
                  New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                  CSDA Barcode Functions

                  CSDA Code Utility
                  CSDA Screen Capture


                  Comment


                  • #10
                    Re: Summary Operation - Unhandled Exception

                    Figured it out.

                    For the record, this is someone else's code I'm now supporting. I thought it was well-tested.

                    I found three fields in the summary operation that were being summarized twice. Took 'em out and all is well.

                    Thanks Stan and Ira for your attention.
                    -Steve
                    sigpic

                    Comment


                    • #11
                      Re: Summary Operation - Unhandled Exception

                      Just out of curiosity I created a summary operation where six fields were summarized twice. Operation and script from that operation both perform as expected. V8.

                      Might be a V10 specific problem?
                      There can be only one.

                      Comment


                      • #12
                        Re: Summary Operation - Unhandled Exception

                        Hi Steve,

                        Originally posted by Steve Workings View Post
                        Figured it out.
                        That's Great!

                        Originally posted by Steve Workings View Post
                        For the record, this is someone else's code I'm now supporting.
                        In this case, that was an important piece of information! I know what to expect from code of yours, but someone else's is a whole different story!

                        Originally posted by Steve Workings View Post
                        I thought it was well-tested.
                        Apparently you thought not! :D

                        Anyway, while I don't think Alpha should error out (Probably worth a bug report), it falls into one of those categories of using Alpha off the path.
                        Regards,

                        Ira J. Perlow
                        Computer Systems Design


                        CSDA A5 Products
                        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                        CSDA Barcode Functions

                        CSDA Code Utility
                        CSDA Screen Capture


                        Comment


                        • #13
                          Re: Summary Operation - Unhandled Exception

                          My client tells me this has run fine before in version 9. This is the first time running it in version 10 and, probably, therefore the error.

                          I suppose I could report a bug, but clean code is a better solution so I'm not going to bother 'em with this one.
                          -Steve
                          sigpic

                          Comment


                          • #14
                            Re: Summary Operation - Unhandled Exception

                            I posted this elsewhere but did not get any feed back.

                            Could you guys please investigate this 'Unhandled Error' that has suddenly appeared in V10. I don't know which build because I am still having to use a build going back to October 2009 and this is OK and has been in all other versions and builds prior to that.

                            A simple one to one set and try to add a new child on a form based on a set. I have used two tables from Alpha Sports to highlight the situation, I need to know if this is a bug because have not had any response from Alpha.

                            Appreciate any feed back on this one.

                            Michael

                            Comment


                            • #15
                              Re: Summary Operation - Unhandled Exception

                              Michael:

                              I can confirm that an unhandled exception is thrown in your form with the latest build. I also tested with build 2659_3515 and it was OK in that build.

                              But I have to ask (rhetorically), since when has it been OK to add fields in a one to one link directly on to a form? I know, I see it all over the place, and in most cases it works. However, I adhere to the evidently considered out-of-date practice of always putting fields from one-to-one links into a sub-form. Do that, and the problem goes away. I added a demo form to your app showing this.
                              Finian

                              Comment

                              Working...
                              X