Gustav Brock
gustav at cactus.dk
Fri May 28 10:38:06 CDT 2004
Hi Charlotte I'm glad you asked - I felt lost here. What pages? Besides, Martin, isn't this contradictory: > What I may have is 100,000 records which have to come down from the > server in one hit. All of them. .. > .. What I am trying to avoid is bringing all the records down the > wire. /gustav > It it has to be updatable, you are now officially in the "unbound" camp. > Unfortunately, Access doesn't provide for an unbound continuous form. > How were you planning on presenting these "pages"? > Charlotte Foust > -----Original Message----- > From: Martin Reid [mailto:mwp.reid at qub.ac.uk] > Sent: Thursday, May 27, 2004 10:56 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Paging Recordsets > What I may have is 100,000 records which have to come down from the > server in one hit. All of them. What I want to do at some point is to > Page them down. First 100, Then Next 100 and so on. > On the Access form I want page 1 of X with navigation to any page the > user chooses. Of course they will need to navigate within each batch of > records they get. > Its much like an ASP application but using Access. I would like to > handle the paging by Stored Procedure on SQL Server rather than ADO but > will give ADO a try. What I am trying to avoid is bringing all the > records down the wire. > The the user can change the order by of the 100000 records and we start > the process all over again. So the form opens they get 100 records > ordered by "A", click next page they get the Next 100 ordered by "A". > They then change the order by to "B" they get the first page again > ordered by "B" and so on and so on. > No filtering is allowed. THEY HAVE TO HAVE ALL 100000 records available. > So we would have standard navigation buttons Next Revord Previous, First > Last but we would also have > Page 1 of X Then a navigation bar by page size even bringing 1000 or > 2000 down would be ok. > Any of this make sense?? > OH and it all has to be fully updatable (<: > Martin