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

Change browse view/scroll "method"?

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

    Change browse view/scroll "method"?

    In version 10 and above an embedded browse always wants to take you to the middle of the browse instead of the top of the browse as it did previously. (Maybe this is true in all browses but I seldom use anything other than embedded browses)

    Is there any way to change this default action?

    FWIW - I've run into some serious issues which seem to be related to this. In a set that is 1:M:1 the last/bottom table has a problem "knowing where it is" when scrolling through the browse. Even just clicking back and forth between a top record and bottom record of the browse causes the same problem. The first few records in the browse "change data" to what's in some other record. This is only a visual issue - the record itself doesn't change but it's confusing as all heck for users. Besides, I haven't found one user yet who prefers this new browse method. I'd sure like to get back to the old method even if I wasn't having these other issues.

    Before someone suggests it, no - this is not an indexing problem. And the exact same app works just fine in v8 but not in v10 or v11. Unfortunately my customer updated without asking me first.

    I do have a "solution" but it [isn't very good]. (trying very hard not to swear after working on this one issue for at least 5 hours) The solution was to create calculated fields for every field that I want to displayin the last/bottom table. The calculation is a lookup() based on the linking value from the middle table so, since there are no issue with that table "losing track of where it is", the calculated values never change. Not a very efficient solution and large numbers of records cause some delay but it works. (Even the column color equations have to use the calculated values or they quit working correctly as well.)
    Tags: None
    #2
    Re: Change browse view/scroll "method"?

    Would


    actualRowSet = <browse>.Scroll_Current_Row as n (row as n)

    help?
    There can be only one.

    Comment

      #3
      Re: Change browse view/scroll &quot;method&quot;?

      Ohhh! A new function I hadn't seen before. Thanks. Unfortunately it probably won't help much when someone is using the arrow keys to scroll through the records.

      I may have found a different solution to the "losing track of where it is" in another thread. Apparently Alpha provided a link to an unofficial update that might fix the problem. I've loaded it but haven't had a chance to test it yet - partly because I have to either rebuild the browse again or find an old copy.

      I was mostly hoping someone knew of a way to get back the old method where the browse defaults to the top line instead of the current record jumping to the middle when scrolling. Maybe some people like the new method but I'm getting really tired of hearing complaints from my customers. This is another of those issues where I believe they (Alpha) should have considered an option choice if somebody really wanted the browse to jump the record to the middle of the browse when scrolling. It's just too unintuitive and, therefore, confusing for users.

      Comment

        #4
        Re: Change browse view/scroll &quot;method&quot;?

        I believe someone else discovered the Upsize genie doesn't work in the unofficial release. Not that it would be a deal killer.
        There can be only one.

        Comment

          #5
          Re: Change browse view/scroll &quot;method&quot;?

          Hi Cal,
          If this set is 1:m:1 and you are using a 2nd browse to show the ONE linked record from the 1st browse; have you thought of just placing the fields from the 2nd browse onto the form instead? Not sure that would help this scrolling problem or not but I use this method on forms and have not noticed what you are describing.
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment

            #6
            Re: Change browse view/scroll &quot;method&quot;?

            Try this as the onfetch code for the embedded browse.

            this.command("current_to_top")
            There can be only one.

            Comment

            Previous template Next
            Working...
            X