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

How do I report a bug when it doesn't happen EVERY time

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

    How do I report a bug when it doesn't happen EVERY time

    Quick question.... How do I report a bug when it doesn't happen EVERY time. I don't know what is causing the buG becaUse it is sparadic. This is using the latest patch 2055. If I knew what was causing it and it was in MY code, I would fix it myself. Examples include...

    Unhandled Exception (Access Violation - The thread tried to read from or write to a virtual address for which it does not have the appropriate access.) Alpha5 will do a forced termination.
    -This one happens here and there sparadically.

    Exception Executing XBasic Instruction
    - This one happens A LOT but you can't duplicate the problem.
    So how can it be a problem with the code?

    An Unhandled Exception was generated.
    - Same here, happens sporadically but cannot be duplicated.

    Does anyone have any tips/advice on how I can correct these myself? Or how to send a bug report when I can't duplicate the error every time?

    #2
    Re: x basic and action scritping

    Hi Nicki,

    Originally posted by NICKI004 View Post
    Quick question.... How do I report a bug when it doesn't happen EVERY time. I don't know what is causing the buG becaUse it is sparadic. This is using the latest patch 2055. If I knew what was causing it and it was in MY code, I would fix it myself. Examples include...

    Unhandled Exception (Access Violation - The thread tried to read from or write to a virtual address for which it does not have the appropriate access.) Alpha5 will do a forced termination.
    -This one happens here and there sparadically.

    Exception Executing XBasic Instruction
    - This one happens A LOT but you can't duplicate the problem.
    So how can it be a problem with the code?

    An Unhandled Exception was generated.
    - Same here, happens sporadically but cannot be duplicated.

    Does anyone have any tips/advice on how I can correct these myself? Or how to send a bug report when I can't duplicate the error every time?
    Intermittent problems are the most difficult to solve if they can not be readily reproduced. However, If you can come up with a sequence that will generate the error rather quickly (even if not every time), send a copy of stripped down code to Alpha.

    The errors you listed above can be caused by your code or by Alpha 5. In your code, some of the possibilities might be things like referencing an array outside it's range, or code that calls more code repeatedly, without ever returning back to the calling code as well as many others. Best way to find your problem code is to disable pieces of code and see if that makes the problem go away.
    Last edited by csda1; 03-06-2009, 04:29 PM.
    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


      #3
      Re: How do I report a bug when it doesn't happen EVERY time

      Originally posted by NICKI004 View Post

      An Unhandled Exception was generated.
      - Same here, happens sporadically but cannot be duplicated.

      Does anyone have any tips/advice on how I can correct these myself? Or how to send a bug report when I can't duplicate the error every time?
      I would really like to find a cause and answer to this error that appears out of the blue with no real pattern.

      Michael

      Comment


        #4
        Re: How do I report a bug when it doesn't happen EVERY time

        Worst thing you can do is NOT report it...

        I'd suggest you wait until it happens again, and then describe in as much detail as possible, exactly the steps you took and what happened. Also emphasise that it only happens intermittently, and include the code run at the time, screenshots etc.

        Comment


          #5
          Re: How do I report a bug when it doesn't happen EVERY time

          Does anyone have any tips/advice on how I can correct these myself?
          Here are some ideas.

          Be conscious of the context in which the error appears. Are you using the app? Are you developing the app? What windows or objects are open? What specific activity was occurring when the error appeared?

          Do you compact your database regularly during development? Why not?

          Do you run your scripts with the debugger on when these errors occur? Why not?

          -- tom

          Comment


            #6
            Re: How do I report a bug when it doesn't happen EVERY time

            An Unhandled Exception was generated
            I still get this and the other errors now but only occaisionally....and, of late, they all have been problems I have created.

            Andrea,
            Worst thing you can do is NOT report it...
            Normally I would agree with this if it was a verified bug or at least something that is reproducible....but these errors, when not produced by the user, are rarely seen and so basically it is not possible. If I were to have reported all the instances of these errors over the years (especially the first years when they happened EVERY day!), I would imagine at least a few hundred reports with no way to know what exactly caused them. I just know that I had placed either crummy code or had code in the incorrect place and once I took it out (once found that is), the errors ceased. I ended up using different approaches or whathaveyou knowing that as I cured the problem by removing the code, it was not a bug.

            If fact, so far I have never had Alpha give the "Unhandled Exception" error on its own---all I received were due to bad coding and also a faulty computer which is another story altogether! I have had some releases freeze up though---more with version 9 than any of the others.

            So how do you fix these things?? Follow Tom's advice of course!! And persevere...it will get better.
            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

            Working...
            X