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

Data Pagination vs List Virtualization

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

  • Data Pagination vs List Virtualization

    What is the underlying difference between Pagination and Virtualization in a List Control.

  • #2
    Re: Data Pagination vs List Virtualization

    Originally posted by njguy View Post
    What is the underlying difference between Pagination and Virtualization in a List Control.
    Data Pagination: Pagination is done on the server. When you navigate to a new page, a callback is made to fetch the records from the server.

    List Virtualization: Pagination is done on the client. All data is downloaded from the server and stored locally. No additional callbacks to get data from the server are made when more records are loaded.
    Sarah Mitchell
    Documentation | Alpha Software Corporation
    Get in the know! Join us for our Weekly Webinars: TransForm Tuesday and Wednesday's Alpha Anywhere Demo and Q&A
    Connect with us: Instagram | Twitter | Facebook | LinkedIn | YouTube

    Comment


    • #3
      Re: Data Pagination vs List Virtualization

      Thanks for the clarification......

      Comment


      • #4
        Re: Data Pagination vs List Virtualization

        I know this is an old post, but just debating which to use. For a ONLINE application, it would seem like Data Pagination is a better choice for loading a list with a lot of data (thousands of records) since not all records need to be retrieved from the server at once. That being said, the documentation seems to suggest the opposite. What am I missing?

        Comment


        • #5
          Re: Data Pagination vs List Virtualization

          Originally posted by Scott B View Post
          I know this is an old post, but just debating which to use. For a ONLINE application, it would seem like Data Pagination is a better choice for loading a list with a lot of data (thousands of records) since not all records need to be retrieved from the server at once. That being said, the documentation seems to suggest the opposite. What am I missing?
          The doc recommends using list virtualization if you're pulling a very large data set down to the client.


          If you're only pulling down a little data at a time with pagination, virtualization is not needed. Pagination requires a connection.
          Alpha Anywhere latest pre-release

          Comment


          • #6
            Re: Data Pagination vs List Virtualization

            I am seeing exactly the opposite from what is supposed to happen with List Virtualization.
            My data comes from a MS SQL database and the query for any of my lists happens in less than a second when querying from SQL Server Management Studio, even on a table with over 11,000 records.

            This should be an ideal case for Virtualization, yet if I enable List Virtualization on any of my lists, the performance slows to a crawl (the opposite effect to what is supposed to happen).
            Using Data Pagination is much faster for me compared to List Virtualization.

            Why would this be the case? What am I missing? It is definitely not the SQL query and something going on in the Alpha environment.
            Alpha Anywhere v12.4.6.3.0 Build 7582-5569 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment


            • #7
              Re: Data Pagination vs List Virtualization

              with all due respect the response re List Virtualization does not make sense to me on connected databases where you expect to be able to make a callback (with Pagination on), it all comes down to how you have set your index's in SQL and only returning the fields you require to satisfy the query. Also keep in mind if you are not using the latest builds with the new Get new count of records check box in the SQL data source settings in AA allowing you to turn it off, then its performing the query twice (wow thats scary). virtualization would only be a goer if you expected to be disconnected while in use in my view.count.GIF
              Insanity: doing the same thing over and over again and expecting different results.
              Albert Einstein, (attributed)
              US (German-born) physicist (1879 - 1955)

              Comment


              • #8
                Re: Data Pagination vs List Virtualization

                We use virtualization with lists of tens of thousands of records - with a connection generally expected. While it takes a little longer to load, the benefits at the client side are still worth it. Much faster filtering with the ability to instantly show summary values are among these benefits.

                Also, we much prefer the speed and flexibility of populating our lists from an Xbasic function emitting JSON. We don't use the lists' built-in query.

                I think we've configured this as well as we can, but it would be nice to find some way (or have Alpha provide a way) to at least display the first records more quickly.

                A side-tip for anyone interested: Don't define a custom field in the List "Field" tab using an Xbasic function if you have a lot of records. That kills performance. Find a way to get what you need with your SQL query instead.
                -Steve
                sigpic

                Comment


                • #9
                  Re: Data Pagination vs List Virtualization

                  I suppose developers just have to test what suits their needs best based and on their own capability and resources rather than just follow general help notes, can be a make of break decision in larger data projects.
                  Might be time to get up from the Dreaded chair for us all. Hope your well Steve.
                  Cheers, Pete.
                  Insanity: doing the same thing over and over again and expecting different results.
                  Albert Einstein, (attributed)
                  US (German-born) physicist (1879 - 1955)

                  Comment


                  • #10
                    Re: Data Pagination vs List Virtualization

                    Yeah, it's all a bit confusing how this is supposed to work.
                    An initial load time of 20-30 seconds for list virtualization (database connected) to see improved performance once the data has been loaded just isn't going to cut it.
                    Alpha Anywhere v12.4.6.3.0 Build 7582-5569 IIS v10.0 on Windows Server 2019 Std in Hyper-V

                    Comment

                    Working...
                    X