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



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


  • Filter
  • Time
  • Show
Clear All
new posts

  • select/case

    Hi Phorum,

    Can someone tell me what is wrong with this? I get the error "extra
    characters at the end".

    case adj_net_1=7
    case adj_net_1=6
    case adj_net_1=5
    case adj_net_1=4
    case adj_net_1=3
    case adj_net_1=2
    case adj_net_1=1
    end select

    BTW, pts_1 and adj_net_1 are numeric and both are calculated fields.

    As always I'll be very grateful for advice,

  • #2
    RE: select/case

    Where are you using this sequence, script, field rule, etc?


    • #3
      RE: select/case


      I suggest you verify the correctness of the calc field expressions.

      -- tom


      • #4
        RE: select/case

        Thank you Ohlen and Tom,

        I have the expression in field rules on table level calc fields. I am
        using the fields in other areas of the app without problems. Now I question whether select/case can be used in field rules.

        Incidently, I put the following in the interactive window:

        dim adj_net_1 as n
        dim pts_1 as n
        adj_net_1 = 5
        case adj_net_1 = 6
        case adj_net_1 = 5
        end select

        Now when I type in ?pts_1 ... it says 1.000000 .... Go figure


        • #5
          RE: select/case


          You are correct. The command structure, like if..then, while..end while, cannot be used in field rules. You should be able to convert your original idea, which looks like a field rule for pts_2, into:

          There can be only one.


          • #6
            RE: select/case


            which looks like a field rule for pts_1
            There can be only one.


            • #7
              RE: select/case


              If you are working on a field rule for pts_1, and adj_net is a calculated field, I assume you are rounding something to get to adj_net being a whole number between 1 and 7.

              Wouldn't a simpler calculation for pts_1 be...

              There can be only one.


              • #8
                RE: select/case


                Thank you, it works like a charm.


                • #9
                  RE: select/case


                  Good thawt, but adj_net_1 thru 18 and pts_1 thru 18 will always be whole numbers.


                  • #10
                    RE: select/case


                    this happens because the interactive window is line oriented, not page oriented.

                    For block structures like If End If sequences, or
                    Select End Select sequences you must type the entire block on one line, using the line separator character (I think it's the semicolon, but you should verify first).

                    this is explained better in the Xbasic Ref Manual

                    -- tom


                    • #11
                      RE: select/case

                      Good point Tom, I'll remember that.
                      Thank you,