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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Code Quit on me?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Code Quit on me?

    I use this code to move from the last field on the first tab of the subform to the first field of the next tab, etc.

    tabbed1.tab_set(2)
    sys_send_keys("{tab}")

    It work great but then quit. I checked my tab order and that's OK. Any thoughts about what I should check out next?

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.
    Tags: None
    #2
    RE: Code Quit on me?

    Hey Kenn
    Is the script on a OnArrive action for an invisible button? That's how I do mine. When you leave the last field on the first tab does it stop on the invisible button or just remain on the last field?

    Basically, if the onarrive button has that script and the button is in the tab stop.. should be firing. Not sure what else would cause it to quit.

    Mick

    Comment

      #3
      RE: Code Quit on me?

      Hi Mick,

      Yes, it is. I recreated the buttons and after creating the first button, I copied and pasted it to the other tabs changing the number. It didn't work. But then, That's what I did the first time and it did work.

      Next, I created the button one at a time for each tab and it works on 4 of the 5 tabs. Haven't a clue why it's not working on the one tab but the tab order is OK and so is the code.

      Note: On a previous post about fonts working on the Enable Font Equation (logical field) if(C_Statem = .t.,"helvetica,12,b","helvetica,12,i") would not work but not it began working. Bill Parker, can youcreate a gremlin search & destroy function for the A5 Documenter?

      kenn
      TYVM :) kenn

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

      Comment

        #4
        RE: Code Quit on me?

        Hey again
        Change the script on the button thats not working from the OnArrive to OnPush. Tab through normally and see if it stops on the non-working button. If so, push it and see if you can manually get it to switch... ahhh the power of elimination, gotta love it.

        Mick

        Comment

          #5
          RE: Code Quit on me?

          Mick,

          No it doesen't. Before and after trying your suggestion, the tab order took me to the tab itself and it skips the button and goes to a button off the tabbed subform. The order # for the button is 8 and tabbed subform is 86.

          OK now some more gremlins. After I first created the buttons and they were working, something happened and they all disappeared. Now, after creating each button again and moving back and forth from design view to form view, they reappeared.

          Wierd!

          kenn
          TYVM :) kenn

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

          Comment

            #6
            RE: Code Quit on me?

            Found the cause? Don't know but this is what's happening. I created a button on each tabbed page and put this code on the button's OnArrive event.

            tabbed1.tab_set(1)
            sys_send_keys("{tab}")

            It work just fine. Then, I went to the button's properties and checkd the Hide box on each button. Now, it's as if the tab stop box is unchecked which it is not. The hide box, when checked is over riding the tab stop box, even though the tab stop box IS checked.

            Uncheck the Hide box and it works again.

            Any suggestions?

            Thanks,

            kenn
            TYVM :) kenn

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

            Comment

              #7
              RE: Code Quit on me?

              Ken,

              I prefer to use the approach outlined at

              http://www.learn alpha.com/FAQs/FAQs.htm


              There, a dummy object (based on a variable I believe) is used instead of a button. Buttons have special properties and 'actions' that simple fields do not. Perhaps one or more of them are getting in the way, when you use a button like this.

              -- tom

              Comment

                #8
                RE: Code Quit on me?

                Kenn, I apologize.

                Dr. Wayne's approach DOES use a dummy button after all. I missed it as I sleepily reviewed the article just now. Jeez, wish there was a way to delete a message!

                Anyway, I still think it's better to use a dummy field rather than a button. All you need is something that will remain in the tab stop order (unlike text boxes).

                -- tom

                Comment

                  #9
                  RE: Code Quit on me?

                  Hey Ken,
                  Glad you found the problem. Hide, disable and read only pretty much render objects null as far as actions/lookups. etc go. Didn't even think about the hide option.

                  My tab jump buttons are invisible, meaning the properties of the button have no border, no text and the fill color is Win3d (Or whatever color your form background is). In design mode the button objects have a faint border so you can see where they are. In view mode, nothing.

                  I also make form exit spots the same way. I have an administration menu that I can call up from any form because they have the invisible exit button (w/ password script) in the same place on every form.

                  Mick

                  Comment

                    #10
                    RE: Code Quit on me?

                    Kenn,

                    Here's an example that uses both variable fields and buttons. Now, off to bed.

                    -- tom

                    Comment

                      #11
                      RE: Code Quit on me?

                      Tom,

                      Thanks for the tip. I'll give it a try.
                      I replied to you under Mick's post because I didn't want to wake you up.

                      Mick,

                      Yes, that's another way of hiding it that I've used before but forgot about.

                      See you at the user group meeting enxt week.

                      Thanks,

                      kenn
                      TYVM :) kenn

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

                      Comment

                        #12
                        RE: Code Quit on me?

                        Hi Tom,

                        An interesting thing I found about the properties of the variable used in this snippet, when the "Hide" box is checked, it does just that. It not only hides it from view but also hides (and literally removes)it from the tab order. Uncheck "Hide" and you're back in business. The same situation with using a button. I have my doubts that this is what Alpha intended.

                        kenn
                        TYVM :) kenn

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

                        Comment

                        Previous template Next
                        Working...
                        X