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

Embedded Browse Pointer Location of Find A5V9 & A5V10

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

    Embedded Browse Pointer Location of Find A5V9 & A5V10

    I have a Form with an embedded browse. The embedded browse is from the same line_item Table.
    In A5V9, when I do a find, the browse pointer finds the first occurrence which is located at the top of the embedded browse.
    In A5V10, the find works as expected, but the first occurrence if located midway in the embedded browserather than at the top of the browse.
    Sounds minor, but my Customer uses this embedded browse to spot check multiple line_items, and the mid-browse pointer causes undue mouse/keyboard input.

    Any thoughts on settings or changes between versions that might have caused this or might alleviate this?

    With best regards,
    Jim

    #2
    Re: Embedded Browse Pointer Location of Find A5V9 & A5V10

    The browse object was largely re-written for version 10.

    If I recall correctly this change in behavior was the result of user requests. You might try searching for related message board threads in this forum to see if there's a work around that will help your customer.

    Comment


      #3
      Re: Embedded Browse Pointer Location of Find A5V9 & A5V10

      See if .scroll_current_row() will help after the find.
      There can be only one.

      Comment


        #4
        Re: Embedded Browse Pointer Location of Find A5V9 & A5V10

        Thanks for the speedy reply Tom. I think in most cases this revised behavior makes sense. Stan Mathews suggested something to try out below.
        Thanks again!

        Comment


          #5
          Re: Embedded Browse Pointer Location of Find A5V9 & A5V10

          Hi Stan,
          Thanks for the suggestion. I will give it a try and let you know.
          Best regards,
          Jim

          Comment


            #6
            Re: Embedded Browse Pointer Location of Find A5V9 & A5V10

            I played with the .scroll_current_row() method a bit with the OnFetch and OnRowChange events. What I was hoping to accomplish was for the cursor to jump to the top record in the embedded browse after doing a CTRL-K Find, and then be able to just navigate freely.
            With either of the events, the browse pointer still started off mid-browse. As soon as I clicked within the browse then the .scroll_current_row() fired as expected.
            What I found out later on is that this new behavior of landing in the vertical middle of a Browse object occurred not only in the embedded browse but also in field Lookups where finds are enabled as well. As a result the users, who used to just look at the top record, now need to scan the middle records. I need to find the setting for Cursor Colors and make this more obvious.

            Thanks again for your help.

            Comment


              #7
              Re: Embedded Browse Pointer Location of Find A5V9 & A5V10

              Hi Jim
              If I assume this is an embedded browse on a form based on the same table.
              The embedded browse is from the same line_item Table.
              then just explain briefly the fundamental relationship/s.
              Does the browse display multiple records with (some) fields sharing the same table as the parent? One thing I have learnt from resolving problems with record selection, nothing happens randomly - the "midway" record has an underlying reason for being selected.
              I chirp in here because I mastered issues with multiple embedded browses referrencing the same basic table. Adding fixes to patch fundamental issues can lead to instability, been there yourself I'm sure.

              Comment


                #8
                Re: Embedded Browse Pointer Location of Find A5V9 & A5V10

                Hi Ray,
                Thanks for your feedback. This particular Form is based on just one table "tbl_wo_items", not a set. The form has an embedded browse (EB) based on the same table.
                They are just doing a simple find and both A5V9 and A5V10 are finding the correct record. What has changed is where that record is located within the EB. In A5V9, the "found" record sits at the top of the EB, whereas in A5V10, the "found" record sits in the middle of the EB.
                The EB is located on the top of the Form and detailed fields and buttons are on the lower half of the form. The customer uses this form to scan and review multiple records and then pops down into the detail form fields for updating purposes.
                As described above, the relative "middle of the browse" positioning after a find became evident even in field lookup "finds". So the changes appear to be systemic/fundamental.
                At this point, the safest path is to help the user more quickly identify the "found record" with formatting options.

                Thanks again for your feedback,
                Jim
                Last edited by jimk7577; 07-04-2011, 02:15 PM. Reason: Spelling error

                Comment

                Working...
                X