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

Double Click Not Setting "Current Record"

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

    Double Click Not Setting "Current Record"

    I have an embedded browse that, "sometimes," when a record is double-clicked, does not seem to set the correct "current record." I think this because, "sometimes," a script associated with the browse's double-click does not get the correct fields values... i.e. sometimes the script seems to be looking at a record above (we think) the record that was doubled-clicked.

    Any thoughts/ideas would be greatly appreciated.
    "all things should be as simple as possible... but no simpler"

    Mike

    #2
    Re: Double Click Not Setting "Current Record"

    Mike,

    What is your code to retrieve the record value?
    Peter
    AlphaBase Solutions, LLC

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


    Comment


      #3
      Re: Double Click Not Setting "Current Record"

      Peter,

      This is the code:

      Browse4:Openings.value>0

      that seems to be getting it's value from the row above the row that was dbl-clicked.

      Thanks,
      "all things should be as simple as possible... but no simpler"

      Mike

      Comment


        #4
        Re: Double Click Not Setting "Current Record"

        Originally posted by michaelwpayton View Post
        Browse4:Openings.value>0

        that seems to be getting it's value from the row above the row that was dbl-clicked.
        Mike,

        Maybe I'm missing something, but I don't understand how that retrieves the value?

        If you are using the doubleclick this might make sense:
        Code:
        If Browse4:Openings.value>0
           vOpenings = Browse4:Openings.value
        End if
        or, maybe:

        Code:
        If this:Openings.value>0
           vOpenings = this:Openings.value
        End if
        Peter
        AlphaBase Solutions, LLC

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


        Comment


          #5
          Re: Double Click Not Setting "Current Record"

          Sorry, Peter... the value is being used in a condition...

          If Browse4:Openings.value>0

          Thanks,
          "all things should be as simple as possible... but no simpler"

          Mike

          Comment


            #6
            Re: Double Click Not Setting "Current Record"

            It "seems" that when this particular embedded browse is loaded, the first record listed is "the current record," even though some other record is flagged with the row pointer.

            Then... if right after loading the browse... the user dbl-clicks any row, without "clicking around" on various rows first, my code operates based the first record listed, regardless of what record they actually dbl-clicked. But, if the user clicks around a bit, then dbl-clicks... all is well.

            Does anyone have an ideas/"things to try" to work around this? Is there anyway I can code something, maybe in the init, to "click around a bit" before the user gets control :-)
            "all things should be as simple as possible... but no simpler"

            Mike

            Comment


              #7
              Re: Double Click Not Setting "Current Record"

              Yes, I just ran into this. The fix is quite easy. Before firing your code, move the pointer one record forward and one record back:

              Browse4.prev()
              Browse4.next()

              then fire your code.
              You can test this by manually moving the pointer (click off of your desired record, then click back onto it), and fire your code. It will select the correct record.

              Best regards,
              Jay Talbott
              Jay Talbott
              Lexington, KY

              Comment


                #8
                Re: Double Click Not Setting "Current Record"

                Michael,
                I recommend some more testing. Do the records in your browse that holds the 'Opening' field have a unique record identifier? Is it listed in the browse? If your records have a unique identifier field, I would add it to the browse for testing and also add a button to the form with:
                Code:
                msgbox(browse4:uniquefield.value)
                I would test to see what record is in focus when "the embebbed browse is loaded" by pushing this button instead of any double clicking in the browse.

                Is it possible that you have a calculated field on the form that uses the total() function?
                Mike W
                __________________________
                "I rebel in at least small things to express to the world that I have not completely surrendered"

                Comment


                  #9
                  Re: Double Click Not Setting "Current Record"

                  Originally posted by Mike Wilson View Post
                  Michael,
                  I recommend some more testing. Do the records in your browse that holds the 'Opening' field have a unique record identifier? Is it listed in the browse? If your records have a unique identifier field, I would add it to the browse for testing and also add a button to the form with:
                  Code:
                  msgbox(browse4:uniquefield.value)
                  I would test to see what record is in focus when "the embebbed browse is loaded" by pushing this button instead of any double clicking in the browse.

                  Is it possible that you have a calculated field on the form that uses the total() function?
                  Mike,

                  The records do have a unique id... that is listed in the browse. When the browse is first loaded, two records are listed... 10214 and 10215, with the rec pointer (from a cosmetic point) pointing to 10215. When I dlb-click, my code is getting 10214... unless I first click on 10214, then click on 10215, then dbl-click. If I do all that, the dlb-click works.

                  I have one calc field, a simple field1 - (minus) field2.

                  Jay,

                  I'm playing with what you suggest... but depending on what's actually listed in the browse, I'm not sure it will work for me.
                  "all things should be as simple as possible... but no simpler"

                  Mike

                  Comment


                    #10
                    Re: Double Click Not Setting "Current Record"

                    Originally posted by michaelwpayton View Post
                    Does anyone have an ideas/"things to try" to work around this? Is there anyway I can code something, maybe in the init, to "click around a bit" before the user gets control :-)
                    Try an alternative method, if you can:
                    Code:
                    t = table.get("tablename")
                    vOpenings = t.Openings
                    Peter
                    AlphaBase Solutions, LLC

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


                    Comment


                      #11
                      Re: Double Click Not Setting "Current Record"

                      Peter,

                      Tried it... doesn't seem to make a difference... I'm still getting the wrong record on dbl-click... unless I click records before ddbl-clicking.

                      Thanks,
                      "all things should be as simple as possible... but no simpler"

                      Mike

                      Comment


                        #12
                        Re: Double Click Not Setting "Current Record"

                        Originally posted by michaelwpayton View Post
                        Tried it... doesn't seem to make a difference... I'm still getting the wrong record on dbl-click... unless I click records before ddbl-clicking.
                        Sounds like another browse bug.
                        Peter
                        AlphaBase Solutions, LLC

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


                        Comment


                          #13
                          Re: Double Click Not Setting "Current Record"

                          I am having a deja vu experience reading this. I am almost positive it came up before.

                          If you want to understand why this happens, try to answer this question:

                          What is the difference between? :
                          1-A double click, and
                          2-Two consecutive single-clicks

                          Comment


                            #14
                            Re: Double Click Not Setting "Current Record"

                            I have exactly the same thing when I click buttons on my embedded browses. I have to hi-light the row prior to clicking the button in some browses. Some browses work perfectly, but others work on a random basis. I think the difference is whether the browse is from a parent or child table. The browses from the child tables are the ones that don't always function correctly - the record at the top of the browse opens instead.

                            Comment


                              #15
                              Re: Double Click Not Setting "Current Record"

                              Larry... that is the case with mine, i.e. a child table which, unless you click around first, dbl-click will be associated with the wrong record.

                              G... Sorry, I've never been any good at riddles.
                              "all things should be as simple as possible... but no simpler"

                              Mike

                              Comment

                              Working...
                              X