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

Unhadled Exceptions in Lookup - Possible Fix

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

    Unhadled Exceptions in Lookup - Possible Fix








    OOPS




    Some users have reported getting an unhandled exception error when using
    Field Rules lookups. We have had a very hard time repeating these problems on
    our development machines.

    We were able to eventually repeat one test case sent in by Jim Chapman
    yesterday, and have the following fix.
    Exit A5 and unzip this file in the A5 program folder.


    http://downloads.alphasoftware.com\Patches\a5v50_1383.zip


    If you have been getting this error, please let me know if this fix works for
    you. If so, then we will release this as the next patch.

    Thanks.

    #2
    RE: Unhadled Exceptions in Lookup - Possible Fix

    Selwyn

    The patch seems to have fixed the problem for me. I took a previous test set that regularly gave the lookup error and entered over 200 entries without any problems at all. Works very well.

    Jerry

    Comment


      #3
      RE: Unhadled Exceptions in Lookup - Possible Fix

      I was having a problem with coping a section of script and moving it to a button. When Alpha was opened for a while, as soon as I went to copy a section of script Alpha would crash. I have not witnessed this today as of yet. But give me time I may find it later. I will let you know. Jack

      Comment


        #4
        RE: Unhadled Exceptions in Lookup - Possible Fix

        You know I am starting to get crashes in the kernel. It is not due to the fix since I installed the last three updates and the behavior is the same. I think it has to do with an activeX control. If someone has the time could you look at this code and see if I am clearing all the cache from the memory or am I just keeping it in memory????

        Filename is the name of the picture location. all the pics are Jpeg. So the size is rather minor. This script is on the ONFETCH of a form and the form crashes if you scroll more than 25 records at a time on an embedded form.

        Here is the code (Just look at the ActiveX coding, I do not understand the wording too well and just experimented until it worked.)

        dim shared filename as c
        if filename"" then
        LitData_new1:activex2.activex.RemoveImageCache(filename,1)
        LitData_new1:activex2.activex.ClearDisplay()
        end if
        t=table.current()
        if filefind.get(A_DB_Current_Path+"Lights"+CHR(92)+alltrim(t.supplier)+chr(92)+(alltrim(T.cat_no))+".bmp")"" then
        filename=A_DB_Current_Path+"Lights"+CHR(92)+alltrim(t.supplier)+chr(92)+(alltrim(T.cat_no))+".bmp"
        elseif filefind.get(A_DB_Current_Path+"Lights"+CHR(92)+alltrim(t.supplier)+chr(92)+alltrim(T.cat_no)+".jpg")""
        filename=A_DB_Current_Path+"Lights"+CHR(92)+alltrim(t.supplier)+chr(92)+alltrim(T.cat_no)+".jpg"
        else

        end
        end if
        LitData_new1:activex2.activex.ClearDisplay()
        LitData_new1:activex2.activex.ImagePut(filename)
        LitData_new1:activex2.activex.ImageGet()
        nW=LitData_new1:activex2.activex.ImageWidthGet()
        nh=LitData_new1:activex2.activex.ImageHeightGet()

        PerW=LitData_new1:activex2.object.width*100/nw
        PerH=LitData_new1:activex2.object.height*100/nh
        if perw>perH then
        zm=perH*100
        else
        zm=perw*100
        end if


        'litdata_new1:activeX2.activeX.FitTo(0)' this command does
        litdata_new1:activeX2.activeX.ZoomPut(zm)'not work alpha
        xbasic_wait_for_idle() 'say no known sLitData_new1:activex2.activex.display()

        Comment


          #5
          RE: Unhadled Exceptions in Lookup - Possible Fix

          This fix has now resolved a problem that I have had since installing Version 5.

          Up until Build 1023 I was unable to save child records based upon a lookup in a one-to-many set. This was based upon not checking the "display as a drop-down list" option. (I need to be able to both add and edit records.) Although I was able to duplicate the problem in the AlphaSports database on my XP machine, the problem did not arise on the majority of XP machines. (It did not occur on my 98 computer.) I have continued to use V. 4.5 to enter data in my applications.

          Based upon a post from another user it appeared that my printer driver (HP Deskjet 970) was responsible. Initially, the problem disappeared after resorting to the XP driver. However, the solution was not permanent.

          With Build 1023, the lookup problem was resolved although, like a number of others, I began receiving the "Unhandled Exception" error message, typically after 3 child records had been entered. Curiously, this did not occur with the AlphaSports database.

          My testing of the posted fix has given me enough confidence to uninstall Version 4.5.

          Craig

          Comment


            #6
            RE: Unhadled Exceptions in Lookup - Possible Fix

            I have done limited testing with the patch, but it works everywhere I've tried it. Thanks, it's a big help.

            Jeff Emery

            Comment


              #7
              RE: Unhadled Exceptions in Lookup - Possible Fix

              The patch works!

              I have seen this problem numerous times with one setup I have been working with. In this setup the "Unhandled exception" error would occur when you first entered into a field located in an embedded browse. The field also had a lookup field rule using a lookup in a separate window. The problem would not occur every time but at least within every 5th entry in this embedded browse.

              This description matches that posted in the past.

              The patch posted here appears to have fixed the problem, I've done at least 30 entries into the same setup with no problems.

              Thanks for the great work everyone. I know this must have been a hard one to track down. I had no idea how I could provide a stripped down setup that could reproduce the problem.

              Comment

              Working...
              X