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 Problem

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

    Multistate Button Problem

    I copied the alphabet (multistate buttons) and browse that is found on the customerbase form of the invoicing app that comes with A5 this form to my app, made the necessary changes and it was working slick. For a reason that I haven't been able to figure out, when clicking on a alphabet letter button, nothing happens. I've checked the code, variables, indexes, etc. Even recopied the buttons and browse from the customerbase form to my form. Still nothing happens when I click on a letter of the alphabet.

    I've concluded that the problem is not an index, is not any of the code on the multistate buttons or the show all button and browse containing the last names nor is the problem with the variables.

    Any idea what else I might check?

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Multistate Button Problem

    Ken, what's the context for your form? Is it based solely on the table that your multi-state button is trying to query? (that's what the invoice example is doing...)

    If it's based on a set, is the set based on a single field link?

    Does the form have a filter or order expression in place that's governing the display of records from the underlying table or tables?

    -- tom

    Comment


      #3
      RE: Multistate Button Problem

      Hello Ken,

      Check the properties of the form and the browse, make sure they are not read only.
      Hope this helps

      Cheers
      Tom

      Comment


        #4
        RE: Multistate Button Problem

        ken,
        try copying the buttons again (on your new form), just copy and then paste. I have found that sometimes you need to re-copy a button object.

        Comment


          #5
          RE: Multistate Button Problem

          Hi,

          Tom Cone - No, Yes, No

          Tom Holt - Read Only is NOT checked

          John - When I copied, I copies the whole thing but will try copying only the buttons.

          I also got an email for Charlie Crimmel with a suggestion. Will work with this when I ge home this evening.

          Thanks, again,

          kenn
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment


            #6
            RE: Multistate Button Problem

            Ken,

            The code in the multi-state button example in Invoices sample is not tweaked for use with a set. If you are trying to query the child table for example, the sample code must be revised to point to the child table instead of the parent. In this situation you are dealing with a variation of the child browse challenge we worked through last fall. Remember?

            -- tom

            Comment


              #7
              RE: Multistate Button Problem

              Hi To,

              Tried everything I can think of and then revisited my thoughts on the set and figured it's like you say so will be doing some re-thinking about this. Thanks for confriming my thoughts.

              ken
              TYVM :) kenn

              Knowing what you can achieve will not become reality until you imagine and explore.

              Comment


                #8
                RE: Multistate Button Problem

                Tom,

                Read through your suggestion too fast. The parent table contains the LASTNAME field so all references are to the parent table. The multistate button should have nothing to do with the child table. Am I missing something here?

                Thanks,

                kenn
                TYVM :) kenn

                Knowing what you can achieve will not become reality until you imagine and explore.

                Comment


                  #9
                  RE: Multistate Button Problem

                  I've found the answer. Much to my dismay. The form is corrupted. I copied the multistate button from the form in question and pasted it onto a new form built on the set. It works fine.

                  I say much to my dismay because I have a tabbed object with lots of time spent writing expression on many fields.

                  Now for another quirk for which I'll make a new post.

                  Thanks,

                  kenn
                  TYVM :) kenn

                  Knowing what you can achieve will not become reality until you imagine and explore.

                  Comment

                  Working...
                  X