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

V6 and V7 testing needed please

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

    V6 and V7 testing needed please

    Bill Belinger was looking to incorporate a form level progressive lookup with a touch screen keyboard.

    I put together the attached example of how he might build the interface.

    I created this in version 6 and it works fine on my machine.

    Bill is using version 7 and the application does not function as expected.

    I don't have version 7 to test on and he does not have version 6.

    Could someone who has version 7 or better yet version 6 and version 7 please test this app and let us know if it works for you in each environment?

    When the app opens, click on the yellow search button on the customer form.

    This will open the search form. Using your mouse, spell the word "OUT" leaving the quote marks out. Please observe whether the top record in the browse becomes Outdoor Resorts.

    Click on the ENTER button. The search form should close and the customer form should now display the Outdoor Resorts customer record.

    Thanks for the help!

    Louis and Bill

    #2
    Re: V6 and V7 testing needed please

    Louis and Bill,

    Just tried in both v6 and v7. Can canfirm that in v6 behaviour is as Louis described and in v7 the filtering does not work. In v7 the enter button results in what ever record was active in the browse on the search form to be active in the customer form.
    Tim Kiebert
    Eagle Creek Citrus
    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

    Comment


      #3
      Re: V6 and V7 testing needed please

      Tim,

      Thank you for checking this out.

      I guess I'll have to dig into the code and figure out what has changed in version 7.

      Louis

      Comment


        #4
        Re: V6 and V7 testing needed please

        I took a quick look but did not spot it straight away. I am in the middle of posting a thread on some different behaviour in filtering between v6 and v7. But from your code I gathered you were using find rather than query so it might not be related.
        Tim Kiebert
        Eagle Creek Citrus
        A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

        Comment


          #5
          Re: V6 and V7 testing needed please

          Louis & Bill,

          In your form the user is not pressing keys on the keyboard. Instead, she's pushing buttons which represent keys. Your script passes the "key" using a sys_send_keys() call to the "choice" text box on your form. You then rely on the form's onkey script to evaluate the text in the "choice" text box depending upon whether the key "up" or Key "down" events are fired. It might be simpler, and would be much more straightforward, if you eliminated all the keyboard handling code. You need not usethe OnKey event for the form to trigger the progressive search. You can simply display the search key which is being built by the user, but use the button pushes themselves to run the search and refresh the browse object. No need to get balled up in all the keyboard handling code. You're not using the keyboard for data entry if you see what I mean. -- tom

          Comment


            #6
            Re: V6 and V7 testing needed please

            Tom,

            I agree. At first glance, it would appear that I have walked all the way around the block to get next door.

            In an effort to illustrate to Bill how Dr. Wayne's progressive lookup works, I built this app to utilize the keyboard. (It's really Dr. Waynes app with a couple of minor modifications). Then to show him how to incorporate the touch screen keyboard functionality, I added the buttons and actions for the keyboard and used sys_send_keys() to emulate pressing keys on the actual keyboard.

            Your suggestion that the application could be more efficient and easier to maintain if the On_Key code was not used are right on the money, and in a finished product, I would probably heed your advice.

            Regardless, it appears that something has changed from V6 to V7 that is causing the script to fail. Unfortunately, I don't have V7 to test with. With that in mind, do you see anything in the On_Key code for the search form that might be causing the problem in the V7 environment?

            As always, thanks for your insight and assistance!

            Louis

            Comment


              #7
              Re: V6 and V7 testing needed please

              But Tom, if you use the keyboard it doesn't work either. So our question is why does it work in 6 and not 7.

              Bill Belanger

              Comment


                #8
                Re: V6 and V7 testing needed please

                Bill,

                Give this a try and let me know if the browse behaves correctly.

                1. Place a new button on the search form.

                2. Copy and paste the following 2 lines of code in the new button's On-Push event.

                table.current().fetch_find("cold")
                browse1.refresh()

                3. Save and close the search form.

                4. Open the customer form.

                5. Press the yellow search button.

                6. On the search form, press the new button you created and see if the browse responds correctly.

                Let me know.

                Louis

                Comment


                  #9
                  Re: V6 and V7 testing needed please

                  browse1.refresh()
                  should fail. The script will need complete path to the object being refreshed... something like this should work:
                  parentform:browse1.refresh()

                  Comment


                    #10
                    Re: V6 and V7 testing needed please

                    Tom,

                    Thank you. Will give it a try.

                    Louis

                    Comment


                      #11
                      Re: V6 and V7 testing needed please

                      Originally posted by Tom Cone Jr View Post
                      should fail. The script will need complete path to the object being refreshed... something like this should work:
                      Tom & Louis,

                      I don't believe the parentform is required. But v7 does not support browse1.refresh(). You must use browse1.resynch() or parentform.resynch() - the latter is usually preferred or required (at least in my experience).
                      Peter
                      AlphaBase Solutions, LLC

                      [email protected]
                      https://www.alphabasesolutions.com


                      Comment


                        #12
                        Re: V6 and V7 testing needed please

                        Peter, I think <object>.refresh() remains a valid method for both forms and the controls on a form. -- tom

                        Comment


                          #13
                          Re: V6 and V7 testing needed please

                          Originally posted by Tom Cone Jr View Post
                          Peter, I think <object>.refresh() remains a valid method for both forms and the controls on a form. -- tom
                          You may be right, Tom. It just does not work for browses in my experience.
                          Last edited by Peter.Greulich; 11-06-2006, 12:53 PM.
                          Peter
                          AlphaBase Solutions, LLC

                          [email protected]
                          https://www.alphabasesolutions.com


                          Comment


                            #14
                            Re: V6 and V7 testing needed please

                            Tom, browse1.refresh() in V7 will not resynch data, whereas in 4.0 through 6 it would - you have to use resynch() instead, and usually form.resynch()

                            I think it refreshes things like color and fonts, though.

                            Louis, I would write a function that used the guts of the script that was added to by pushing the button - like for the "A" button set a variable to "A" and call the function adding it to another variable which would then search

                            you could put the same code under each button - like somevariable = this.text abd call the function, or even
                            function_name(this.text)
                            Last edited by martinwcole; 11-06-2006, 02:56 PM.
                            Cole Custom Programming - Terrell, Texas
                            972 524 8714
                            [email protected]

                            ____________________
                            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                            Comment


                              #15
                              Re: V6 and V7 testing needed please

                              Martin, Peter, Tom & Tim,

                              Thanks for your input and suggestions.

                              I will work with Bill to find resolution for this in version 7 and post the results here for all.

                              Thanks again,

                              Louis

                              Comment

                              Working...
                              X