The easiest ways to accomplish this sort of thing are to use a dropdown or an HTML table (such as a datagrid) instead of links, but...
Also, I'm not sure how you do this in classic ASP, but in ASP.NET:
If you must use a link, one relatively easy way is to place a DIV or SPAN or similar element at the top of your form. Give it an ID and set runat=server. Use flow layout for the element.
In the code-behind, you will, of course, know how many items were selected and what page the user is on. This info will be either in session state or view state.
Based on the number of items selected, you compute the number of pages. In the code-behind, somewhere like page prerender, you add link controls to your DIV. Say its ID is "header", in
VB.NET:
[This code is all sort of fuzzy, because I don't have access to Visual Studio right now, but you should be able to look it up and fix the problems.]
dim oA as control
for i=1 to nPages
oA=new htmlsubmitbutton [or whatever the ASP.NET is, I forget]
oA.text=i.tostring
oA.ID="GoTo" & i.tostring [or whatever property it is, if not ID]
Me.header.controls.add(oA)
next i
oA=nothing
This (or something similar) should give you a sequence of submit buttons. In the page load handler, you can check the Request.Item collection to see if one of the GoTo buttons was clicked, and you can then display the correct set of jobs/items.
There are probably dozens of other ways to do this, too, but that's what comes to mind.
-Van
Old dog learning new tricks...