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

Xbasic run in editor -v- Xbasic run from button

  • Filter
  • Time
  • Show
Clear All
new posts

  • Xbasic run in editor -v- Xbasic run from button

    I have a script that counts members of a number of clubs, also deaths, numbers of joining, resignations etc.

    I couldn't get this to run in a report.

    So I wrote an Xbasic script - runs great in the editor and the totals are correct.

    But when I place a script_run instruction on a button to run this script, none of the totals appear - they are all zero. Why should this happen?

  • #2
    RE: Xbasic run in editor -v- Xbasic run from butto


    To troubleshoot this I'd add a line or two at the end of the script to display the results in a ui_msg_box().

    Alternatively, I'd modify the script to write the results to the trace window.

    Purpose of this is to verify that your script runs ok from the button. If so, it is a good indicator that you have a display problem, perhaps a need to update, refresh, or resynch a field on your form.

    If the script doesn't run correctly from the button, the first thing I'd check is verifying that the script succeeds in opening whatever table is needed to do the calculation. If the table is opened already (i.e. it's a table upon which the form is fully or partially based), then there may be a naming conflict when your script tries to open the next instance of the same table. Check the docs on the command if this is the case.

    -- tom


    • #3
      RE: Xbasic run in editor -v- Xbasic run from butto

      Assuming that you used Script_Play("Scriptname") and not Script_Run("Scriptname") -which is not a valid Xbasic method -

      If the script is run from a button which also issues the print report command, you will need to dimension as global the variables for the totals you calculate in the script AND will neeed to add those same variables as global to your report.

      Finian Lennon


      • #4
        RE: Xbasic run in editor -v- Xbasic run from butto

        Script_run was an A5v1 command. It is probably still supported by version 4 but not recommended. I believe it reacts slightly differently as well but it's been a long time (years) since I compared them.
        Syntax: script_run(Script Name, Data Dictionary Filename)


        When you run the script in the editor, where do the results appear? In a message box?

        You might consider putting the script in your message here or attach it in a text file if it is large. I'm sure at least one person will review it.


        • #5
          RE: Xbasic run in editor -v- Xbasic run from butto

          Thanks for reponses

          I should have added that I put a debug(1) at the end of the script and checked the results in the watch window. This is how I can be certain that the figures are there when run from the code editor, and zeros when run from the button.

          The button was set up using the button genie and carries the instruction "run script .


          • #6
            RE: Xbasic run in editor -v- Xbasic run from butto


            In many areas of Alpha Five context is everything.

            The fact that the script runs correctly in one setting (in script editor)... does not mean, necessarily, that it will run correctly from a button on your form.

            I suggest you try the ideas suggested in my first post.

            -- tom


            • #7
              RE: Xbasic run in editor -v- Xbasic run from butto

              Here's a thought.

              Since you say you verified the results are correct in the script, but the totals are zero, have you checked if the variables are GLOBAL or LOCAL?


              • #8
                RE: Xbasic run in editor -v- Xbasic run from butto

                Thanks to everyone for their help.

                I decided that it was probably easier to rewrite it completely in the form rather than in the global scripts and it now works fine.

                I still do not understand why the script produced different results when run in different areas of the programme. However I have the results I need, so I shall stop worrying about it.