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

A/S set Variable to Constant or Expression

  • Filter
  • Time
  • Show
Clear All
new posts

  • A/S set Variable to Constant or Expression

    The Action Script "Set Variable to Constant or Expression", instructions indicate that you must NOT surround constants with quotes.

    Attached sample 1 works fine. Checking for a blank date {}.

    Attached sample 2 does not work because I cannot figure out how to indicate a character blank without using quotes e.g. " ". Also if I remove the quotes fro "A" I get error message "Invalid or incomplete expression ?

    As always, any suggestions appreciated.

    Thanks, John

  • #2
    John, which image is sample 1 and which is sample 2? I confuse easily. :)

    Assuming Script Variable 1 is sample 2, I don't see anything wrong. Have you misspelled something? The use of quotes to denote an empty character string is permitted. I just used the following expression successfully in an action scripting statement in the OnPush event for a button on a form:

    =if(var->A = "","Empty","")
    -- t
    Last edited by Tom Cone Jr; 12-13-2005, 04:01 AM.


    • #3

      Apparently the AS script editor does NOT want quotes. If I set the variable using the interactive editor, then run the script all is well. It appears the AS script is ignoring the action due to the quotes. Spelling appears OK.

      See attached.

      Thanks for your response. Off to work, will check back this evening.



      • #4
        John, I entered the expression using the expression builder. There's a button (icon) on the AS dialog to open the expression builder, it has a small X-Y image and it located at the right edge of the text box you're typing in when you enter the expression...

        -- tom


        • #5

          Have used the expression builder and it appears ok. However when I run the script it just does'nt work.

          I will reduce the app & post a sample as as soon as I can. Problem is its large integrated app & not easy to reduce.

          Thanks, John


          • #6

            I have reduced the app to bare minimum & zipped up with instructions on how to duplicate the problem.

            If you have the time I would appreciate if you could have a boo at it.

            Thanks, John


            • #7
              Sorry, can't get past the login screen. Password won't work. -- t


              • #8

                Password = Carriage return



                • #9
                  Originally posted by John Gamble

                  Password = Carriage return


                  Well, that sure makes me feel foolish!

                  John, I think the prohibition against using quote marks is only applicable when you are entering a constant. I think it is permitted to use quote marks when entering an expression (which is denoted by the leading equals sign, in this context).

                  For example.

                  I duplicated your MainMenu form and changed your red square button's script so that it does three things:

                  a) assign a null string to the variable, using the default value option in the xdialog
                  b) read the variable, and if it's empty, assign "A" to it or if it's not empty assign "P" to it.
                  c) display the variable in a message box.

                  Everything works predictably. The action script is NOT having trouble detecting whether the variable is empty.

                  Unzip the attachment to an empty folder. Open my form (TomsMenu) and explore the script. When you test this leave all the input fields empty, and just click the OK button.

                  In your Menu form the red square button script assigns a default value of "A" to the variable. Mine assigns an empty string. Then the null is detected, and a second assignment places the "A" there.

                  I don't have time to untangle this but it seems to me that the problem you're having may lie within the expression used to filter the report. The absence of parentheses to separate the various boolean components of the filter expression meaningfully may be causing order of precedence issues which you may be overlooking.

                  -- tom
                  Last edited by Tom Cone Jr; 12-14-2005, 03:49 PM.


                  • #10

                    I think you accidently zipped & sent my original data back.

                    Thanks, John


                    • #11
                      Nope. Check the Forms tab of the control panel for a new form named "TomsMenu" -- tom


                      • #12

                        Allright, so I'm blind as well as suffereing from sometimers.

                        Thanks again, John