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

Error on executing field rule lookup: "Call was Canceled"

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

    Error on executing field rule lookup: "Call was Canceled"

    So I have a table that has a field (N,3,0).

    In the fieldrules, this field has a lookup designed, that offers choice from another table using a linking field and a filter on the external table to get the right records. The filter is matching a field from the lookup table to the contents of a variable set before entering the form where the field rule executes.
    The lookup is displayed as a drop-down list box, forcing closest match and popping up on entrance. There is a specific browse designed for the lookup.
    No error messages appear upon designing the field rule. Everything seems to be OK there.

    Note: I used exactly the same system in a v9 application and it worked (and still works under v9) as a charm. Actually, I just added the table including the field rules from this specific v9 application (copy, paste, adding table) and although it worked without error in v9, under v11 it produces an error message on execution.

    What happens?

    I start with a lookup table that has records, but the field that gets looked up has a value of 0. So, not "empty" but 0,00.
    I open the form on my table, and when I reach the field concerned it opens the dedicated lookup browse, and is showing the available records. No probs till here. Then, I click on the desired record, and next it fills the fields of the form table (as far as I can see nothing is going wrong actually!) BUT it produces at the same time an info dialog box saying:

    ERROR
    i
    "Call was canceled"
    OK

    So, brothers in arms, what the hack is that?

    It does not seem to have any strange consequence besides showing the error box.... values are entered correctly by the lookup as it seems. Nothing is left out or discarded as far as I can see. The value 0,00 is nicely put in the right field as shown on the form.

    So, why the strange info box??

    Clicking OK allows me to go on, without any problem shown.

    This also happens in a second field rule table lookup I defined, but there the field that I looked up had not the value of 0,00 but an actual value. So this seems not to be the problem. However, the same info box appears. And again, normal import of the value without any visual residing problems.....

    The strange thing is, that when I enter the SECOND record in the table that uses the field rule lookup, this behavior is NOT duplicated....
    So it only happens with the first record that I put in the table. Why??

    When I manually check the value of all fields later by opening the tables, I can find no value problem and everything looks ok.

    I have tried this various times, and the problem gets duplicated any time.

    Who can help me out with this? I don't want an error box displayed to the customer when there is nothing actually wrong of course.
    What changed in v11 to make this box appear now, where it does not under v9 ?
    How to get rid of it?

    Thanks in advance for any of your help!

    #2
    Re: Error on executing field rule lookup: "Call was Canceled"

    I can't answer your question. I suggest you delete all the rules for the table, compact your database, then reconstruct the rules using v11.

    Comment


      #3
      Re: Error on executing field rule lookup: "Call was Canceled"

      I understand what you are saying and why. I have encountered more corruption over the last years in the code behind the table field rules where the solution you described worked. However, in this case I already DID that for that particular field, to no avail. Strange is also, that it works ok, just the box pops up, and only with the first record.....

      Comment


        #4
        Re: Error on executing field rule lookup: "Call was Canceled"

        Can you post an example?
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


          #5
          Re: Error on executing field rule lookup: "Call was Canceled"

          It seems I have trouble creating the desired example, because the necessary files according to Alpha are "bound and secured to another workspace".

          Tried to find a solution, but the links to other tables are numerous, one should almost need to post the entire application it seems to deliver the working example. Maybe I can duplicate the problem in something new/small, let's see....
          Last edited by mronck; 11-23-2012, 12:15 PM.

          Comment


            #6
            Re: Error on executing field rule lookup: "Call was Canceled"

            Originally posted by mronck View Post
            It seems I have trouble creating the desired example, because the necessary files according to Alpha are "bound and secured to another workspace".

            Tried to find a solution, but the links to other tables are numerous, one should almost need to post the entire application it seems to deliver the working example. Maybe I can duplicate the problem in something new/small, let's see....
            You have a master password on the database. Also split off when there are links adds to the complication...

            A simple example is definitely the way to proceed...
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


              #7
              Re: Error on executing field rule lookup: "Call was Canceled"

              I managed to create an example, and, hack who would know, the error occurs there as well.....
              I zipped the example database into a file, it is attached to this post: Example.zip

              So here is how you can duplicate the error message:

              1) Unzip the database and open it with Alpha V11
              2) Go to forms, open the Exampleform with "view"
              3) The "Nr" field is autoincrement, enter on it.
              4) Click the arrow to the right at the field "Customer Name"
              5) Select "1 | Hank Chippendale | Holland"
              6) Wait a second, sound is heared and error box "Call was canceled" pops up....

              I am glad I got it to be reproduced.....

              Hope you can find a cause and a solution.
              Again: as far as I can see, this is new behavior. Exactly the same setup in V9 worked (did not check with example).


              Edit: after further testing I can now confirm, that this error does NOT appear in V9.....
              Attached Files
              Last edited by mronck; 11-23-2012, 03:26 PM. Reason: Further testing

              Comment


                #8
                Re: Error on executing field rule lookup: "Call was Canceled"

                Marcel

                I was confused about the number field in the 2 tables. So I made another field called NR and made it a autoinc and left Number as a user entered with the FR lookup filling in the customer number into number of example table.

                That appears to work without the error..

                Attached is the database with the changes I made.

                Not sure what you are trying to do with the fields and why it worked in v9 and not now...(I did this work in 10.5)

                Hope this helps..

                Example_al.zip
                Al Buchholz
                Bookwood Systems, LTD
                Weekly QReportBuilder Webinars Thursday 1 pm CST

                Occam's Razor - KISS
                Normalize till it hurts - De-normalize till it works.
                Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                When we triage a problem it is much easier to read sample systems than to read a mind.
                "Make it as simple as possible, but not simpler."
                Albert Einstein

                http://www.iadn.com/images/media/iadn_member.png

                Comment


                  #9
                  Re: Error on executing field rule lookup: "Call was Canceled"

                  Originally posted by Al Buchholz View Post
                  Marcel

                  I was confused about the number field in the 2 tables. So I made another field called NR and made it a autoinc and left Number as a user entered with the FR lookup filling in the customer number into number of example table.

                  That appears to work without the error..

                  Attached is the database with the changes I made.

                  Not sure what you are trying to do with the fields and why it worked in v9 and not now...(I did this work in 10.5)

                  Hope this helps..

                  [ATTACH]33924[/ATTACH]
                  Hi Al,

                  Your example doesn't work under v11 either..... same problem.... "Call was canceled" Error appearing....
                  Can you confirm that MY example did, or did not, work under v10.5 ?


                  First about the "number" field in my example. Those are just incremental record number fields. The number field in the nametable is supposed to hold a recordnumber (incremental) for each record in the nametable, and the number field in the exampletable is supposed to hold the record number for the record in the example table. The number field in the nametable is NOT supposed to come with the table lookup from the exampletable. As you can see in my example of the exampletable, in the lookup the number is just shown, not filled in any field in the exampletable. It is just there to show what the record number of the record browse is where you can choose from in the lookup. That is why it has no fill value in the lookup. it is not used in the lookup to fill any other field, just for display purposes during the lookup.

                  Also, in your example: I deleted all records in the exampletable and packed it. To be sure to start with no records.
                  Then, when entering a record in the example form, the number appears in the customer name field although that is not how it was mapped in your field rule lookup! Did you see that? So now I ended up with value "1" in the "Nr" field in the forms browse, and the value "1" in the "Customer Name" field in the forms browse? You could that happen?? If you look at the field rules in your example, Nametable->Name is supposed to fill "Customername". However, it does not..... strange?

                  Comment


                    #10
                    Re: Error on executing field rule lookup: "Call was Canceled"

                    The error occurred in 10.5 with what you sent me.

                    Switch the field rule list to put name first and then number and then the name will appear correctly...

                    I'll try v11 later... gotta run for now..
                    Al Buchholz
                    Bookwood Systems, LTD
                    Weekly QReportBuilder Webinars Thursday 1 pm CST

                    Occam's Razor - KISS
                    Normalize till it hurts - De-normalize till it works.
                    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                    When we triage a problem it is much easier to read sample systems than to read a mind.
                    "Make it as simple as possible, but not simpler."
                    Albert Einstein

                    http://www.iadn.com/images/media/iadn_member.png

                    Comment


                      #11
                      Re: Error on executing field rule lookup: "Call was Canceled"

                      I just tried your example exactly as you posted it ? I don't understand the switching you propose either, shouldn't it just work as it is now? As I see it, it should not matter in what sequence your fields are mentioned in the lookup, they should fill as programmed without that being dependent upon any sequence? Or do you mean something else?

                      Anyway. Your example (as you posted it) did not work under v11 as well......

                      Comment


                        #12
                        Re: Error on executing field rule lookup: "Call was Canceled"

                        Marcel, I've tweaked Al's example. No longer uses a coded field rule lookup sequence.

                        Check this screencast.

                        Comment


                          #13
                          Re: Error on executing field rule lookup: "Call was Canceled"

                          Originally posted by mronck View Post
                          As I see it, it should not matter in what sequence your fields are mentioned in the lookup, they should fill as programmed without that being dependent upon any sequence?
                          As Tom stated, it's called a coded filed rule lookup and the sequence does matter...

                          Doesn't work - does that mean you get an error or you get a number displaying rather than a name?

                          Works as expected for me in v11...
                          Al Buchholz
                          Bookwood Systems, LTD
                          Weekly QReportBuilder Webinars Thursday 1 pm CST

                          Occam's Razor - KISS
                          Normalize till it hurts - De-normalize till it works.
                          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                          When we triage a problem it is much easier to read sample systems than to read a mind.
                          "Make it as simple as possible, but not simpler."
                          Albert Einstein

                          http://www.iadn.com/images/media/iadn_member.png

                          Comment


                            #14
                            Re: Error on executing field rule lookup: "Call was Canceled"

                            Hi Al,

                            To be honest with you: I did not even know that a "coded field rule lookup" even EXISTED.... .
                            I have been out a couple of years.... although I am not even sure THAT matters... has it been introduced after v9? Or was it always there already?
                            I will dive into this next thing Al, it seems that the solution lies in that direction.

                            @ Tom: much obliged for your efforts Tom. I must say these screencasts for these type of problems work fantastic! Thank you very much for taking that effort, I really appreciate this.

                            I have been working with Alpha for decades already. Seems one never stops learning, does one?

                            I will report back in this thread as soon as the problem is solved. First some studying regarding this lookup type!

                            Comment


                              #15
                              Re: Error on executing field rule lookup: "Call was Canceled"

                              Marcel, coded field rule lookups have been around a long long time.

                              Check the Invoice_items table in AlphaSports. Have you ever wondered how the full product description appears in the product_id column when browsing the table? The product_id field is CHARACTER, 12 ... so how can the longer text strings be appearing? Alpha is storing the ID in the field, but displaying the DESCRIPTION. How? using the Coded field rule lookup for the product_id field in the invoice_items table. I rarely use this feature. Makes my head hurt. But others swear by it. Still others stumble into it by accident, and I think that's what happened to you.

                              Comment

                              Working...
                              X