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

ON ERROR GOTO in an Action Script Bug?

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

    ON ERROR GOTO in an Action Script Bug?

    Is this a bug?? I have a Action Script which includes inline Xbasic code. The Xbasic code includes ON ERROR GOTO for trapping run-time errors. The basic format for the code is taken right out of the book. In short the routine previews a report. The name of the report is taken from the variable RPT_NAM which has been load earlier. If the report is not found or the variable is blank, the error routine is invoked.

    ON ERROR GOTO PREVIEW_ERR
    :REPORT.PREVIEW(RPT_NAM)
    END

    #2
    RE: ON ERROR GOTO in an Action Script Bug?

    What did I do wrong?? Reposting the code from my first post. Hope it displays the way I intended. Sorry

    ON ERROR GOTO PREVIEW_ERR
    :REPORT.PREVIEW(RPT_NAM)
    END

    Comment


      #3
      RE: ON ERROR GOTO in an Action Script Bug?

      John,

      Don't use Onerror in an inline basic of an action code. The action code has it's own Onerror trapping. Better to create it directly in xbasic (use convert ot xbasic) and eliminate any Inline script code at the top and bottom.

      Regards,

      Ira J. Perlow
      Computer Systems Design & Associates
      [email protected]
      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


        #4
        RE: ON ERROR GOTO in an Action Script Bug?

        The only reason I am posting one last message to this thread is to save someone else down the road the trouble of getting into the trap I found myself in.

        As suggested, I converted the Action Script to inline Xbasic and removed the Action Script error handling code in the Xbasic. I was still not able to achieve what I was trying to do.

        After more tinkering and experimenting the light came on (actually I proved it to myself). ON ERROR GOTO applies to the entire script, not a block of code. Some languages support error handling for separate lines or blocks of code and I made the assumption (and we all know assuming is dangerous) this was true in Xbasic. I was under the impression that the �END� statement as shown in the reference manual�s example was tied to the �ON ERROR GOTO� statement (such as END IF, END FUNCTION, etc.). The code replacing " �put Xbasic code here" was the block of code that would invoke error handling for a run-time error and error handling was terminated by the �END� statement with the script continuing to execute. I now know the �END� statement in the example is for the entire script, not ON ERROR GOTO.

        When I finally figured this out I again re-read the section for ON ERROR GOTO and realized that I should have picked up on this tidbit, but missed it every time I read the section. Maybe it is just me, but I think the ON ERROR GOTO text could be a bit more explicit, but at the same time, I won�t get screwed up by error handling again.

        So once again, after spending a great deal if time tinkering, I have been educated. I think I have also learned it is best to �think stupid� when working in Xbasic - forget my years of experience in programming - it just gets me in trouble.

        Comment

        Working...
        X