There is a way of displaying 4000 plus lines of data even if the server only allows say 250. It involves breaking down the 4000 plus view into smaller views and for speed use of a profile document as follows:
Assume your 4000 plus view is ordered alphabetically. Break down the view into 26 hidden views
Views
Example Field is LinkName and assumes it is unique in each case
Selection formula Select Form = FormName & (@UpperCase(@Left(LinkName ;1))="A") etc
This is required to ensure that the Domino server does not do 26 massive lookups each time you want the data - instead use a profile document with 26 computed @DbColumn fields and an agent that refreshes the profile doc every X mins or hours
Then on your display form create 26 fields that lookup the relevant profile doc fields.
Provided you are careful you should not hit the @DbColumn maximum size or the maximum field size constraints. The result is that the Domino server will refresh the profile doc in the background and the display form will do a quicker live lookup on loading. Page will still take a while to load but you can get your 4000 plus lines if you need them.
All of above assumes that you are happy for the data displayed to be a little bit stale.
Pat
There is a way of displaying 4000 plus lines of data even if the server only allows say 250. It involves breaking down the 4000 plus view into smaller views and for speed use of a profile document as follows:
Assume your 4000 plus view is ordered alphabetically. Break down the view into 26 hidden views
Views
Example Field is LinkName and assumes it is unique in each case
Selection formula Select Form = FormName & (@UpperCase(@Left(LinkName ;1))="A") etc
Write your column appropriately e.g
"<TD NOWRAP><FONT SIZE=1 FACE=\"Verdana\"><b>ยท</b><A HREF=\"/" + @Subset(@DbName ; -1)+ "/0/" + @ReplaceSubstring(LinkName ; " " ; "+") + "!OpenDocument\"> " + LinkName +"</A></FONT></TD></TR>"
Now for the use of the profile document
This is required to ensure that the Domino server does not do 26 massive lookups each time you want the data - instead use a profile document with 26 computed @DbColumn fields and an agent that refreshes the profile doc every X mins or hours
Then on your display form create 26 fields that lookup the relevant profile doc fields.
Provided you are careful you should not hit the @DbColumn maximum size or the maximum field size constraints. The result is that the Domino server will refresh the profile doc in the background and the display form will do a quicker live lookup on loading. Page will still take a while to load but you can get your 4000 plus lines if you need them.
All of above assumes that you are happy for the data displayed to be a little bit stale.