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

Multistate button question

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

    Multistate button question

    In trying to create a multistate button of the type found in alpha sports, I get an expression not valid message when I try to use the expression left(child_last,1).
    I am working with a set which is one to many (student_data to absences). The variable vcletter also does not show on the list of variables. I have run through the modal/modless posts but don't see anything about problems within a set.
    I also get the same error with every other field that I try.

    Thanks for your help
    Jim

    #2
    RE: Multistate button question

    Others may be clairvoyant, it took me several attempts to find the mulltistate button. Also you do not mention where you are trying to use the expression left(child_last,1).

    vcletter is defined for the form in Alphasports and that is why it is visible (in the drag drop list, is that what you meant), is it in yours?
    There can be only one.

    Comment


      #3
      RE: Multistate button question

      Thanks for your reply.
      I was referring to the mustistate button on the customer form in the alpha sports sample that filters the last name of the customer.
      I named the vaiable (session level) vcletter as it was in the alpha sports example.
      The field that is being filtered is called child_last
      I first thought it might be the fact that I was using a set but that turns out not to be the case.
      In desperation I tried reducing the size of the table. It currently has 88 fields. When I did that the button worked fine. The question now is what might be the maximum number of fields in the table?

      Thanks
      Jim

      Comment


        #4
        RE: Multistate button question

        Well, I jest tested that theory more carefully and still does not work.

        Jim

        Comment


          #5
          RE: Multistate button question

          Name it what you please....

          Open the customer information form in the AlphaSports app, design mode. From the menu bar at the top, select "form", "variables". You will see vcsearchby and vcletter. If you do not set up the variables on "your" form in the same manner, they will not be available in the drag-drop list.

          I just added a new variable to my copy of Alphasports, customer information form and it appeared immediately in the drag drop list. If this is what you are doing and not getting the same results, please advise.

          "The field that is being filtered is called child_last" - how are you trying to filter on this field? Can you attach a small sample database?
          There can be only one.

          Comment


            #6
            RE: Multistate button question

            In the attendance database, open the attend entry form.
            In the onchange event for the multistate button use the action scripting to select query, run a custom query, choose expression. Make the expression read left(child_last,1), click ok and you get an invalid expression message.
            Thanks for checking this
            Jim

            Comment


              #7
              RE: Multistate button question

              Jim,

              Had trouble with your zip file. Only one table, AttendHeader included. No form. The other tables appear to be stored in a different folder on your machine and weren't apparently included in your zip.

              Recommended development technique is to always have all the tables in the same folder. Helps prevent problems like this.

              -- tom

              Comment


                #8
                RE: Multistate button question

                Sorry about that, I duplicated from the original database to a new folder and must have made some mistake.
                At this point I need to get some sleep. I have minor surgical procedure tomorrow so I may not get to this for a few days
                Jim

                Comment


                  #9
                  RE: Multistate button question

                  here it is

                  Jim

                  Comment


                    #10
                    RE: Multistate button question

                    Was rather strange. Didn't want to recognize the vcletter variable until I dropped an instance on the form, then edited the onchange event of the multi.

                    I would recommend you rename student data to student_data or plain "students". Can't fathom why your dummy table needs "table" in the name either, why not just dummy. The reason to avoid spaces in table (and field names) is that spaces can cause trouble where Alpha tries to interpret a character sequence and encounters a space where it is not expecting one.
                    There can be only one.

                    Comment


                      #11
                      RE: Multistate button question

                      Thanks for looking at this. In your example it works as it should. I did the following. Opened the form, clicked variables and added the double quotes to the vcletter variable. Placed an instance of the vcletter on the form. Went to the expression box in the onchange event of the multistate button and entered the formula and still get the error.I'll attach it to the next message.
                      Jim

                      Comment


                        #12
                        RE: Multistate button question

                        here is the second attachment
                        Jim

                        Comment


                          #13
                          RE: Multistate button question

                          No! Here it is!
                          Jim

                          Comment


                            #14
                            RE: Multistate button question

                            Once more

                            Comment


                              #15
                              RE: Multistate button question

                              There's no code for the onchange of the multistate on the form in the sample you attached. Are you sure you're working on the correct copy?
                              There can be only one.

                              Comment

                              Working...
                              X