If I understand you correctly somehow your doing the query limiting it to x
records then doing it again to get the rest?
Anyway if you use the search builder as a starter and tell it to limit to 25
then show multiple pages if total is exceeded it will find the whole record
set and just show 25 of the array then when you click on next it will show
the next 25.
It does a nice job or coding all the buttons etc.
If you don't want to do that then drag over the search action choose the
same limits for your results and then code the previous and next yourself.
Basically your at rows start and stop of the array is 1-25 then 26-51 etc.
Once query then just displaying the results from the array stored in memory.
Will be very fast.
Dan
on 6/27/02 5:12 AM, robert at [EMAIL PROTECTED] wrote:
> hi if have a question about sql a have a query that takes in access about 4
> to 5 seconds
> and in sql it takes 2 to 3 second so make the the query
>
> but the problem in that when i want to use the sql query in access it show
> 10 record and when i scroll down
> it need to get the next 10 record from the sql server but then 2 second to
> get the next record
>
> so when i go tru the hole record set it takes me 30 second in sql
>
>
> but in access makes the hole recordset availible in 1 time so it only takes
> me 4 to5 second
> is there a way to make the sql query faster
>
> greeting robert
>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
--
Dan Stein
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Mobile: 610-256-2843
FMP, WiTango, EDI,SQL 2000
[EMAIL PROTECTED]
www.dss-db.com
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
