Paged results with embedded view

Hi,I’m trying to write a view template (and avoid using a search template) with paged results (25 documents per page) and using single category in the embedded view. It’s for use on the web. How do I get the number of documents selected in the embedded view so I can accurately generate the links to navigate among result pages?

I mean the kind that you see in search engines, like Google:

Previous 1 2 3 4 5 6 Next

Subject: Paged results with embedded view

Ok . . from designer help:"Linking to the next and previous pages

In a Web view, @DbCommand with “Domino” as the first parameter pages down and up:

@DbCommand(“Domino”; “ViewNextPage”)

@DbCommand(“Domino”; “ViewPreviousPage”)

Note When called from an action on a page or document in a Web application, @DbCommand acts on an embedded view in the same page or document."

This will page forward and back through the embedded view - but only give you forward and back links / buttons . . . not prev12345next buttons/links.

I found that it’s best for embedded view on the web to limit the amount of data they show by showing for example just one user choose-able category at a time.

To do 25 reults per page, you would use the urlcommand “openform” with the &Count=25 appended on. Yes you are opening a form, but it has a view in it, so it excepts the view parameters as if it was a view url command. Just to be safe, also put a field called savedoptions on the form with the embedded view with value of “0” (text) to ensure it never gets saved as a document.

Subject: How about hiding the buttons when there is no more result before or after the current page?

Thanks Michael. That’s really great help. I got the “Previous” and “Next” buttons now.

But still, how do I get the number of documents in the embedded view so I can properly hide the next and previous buttons? ^_^?

Subject: RE: How about hiding the buttons when there is no more result before or after the current page?

This is exactly what I’m trying to figure out now. How to know the count of actually returned view rows. This is the only piece missing in my paging code.

There has got to be a way. But how?