you have to do this:
barneyb
> -Original Message-
> From: Mosh Teitelbaum [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 19, 2003 11:54 AM
> To: CF-Talk
> Subject: RE: Large Recordset Display Problem
>
>
> My apologies.
> Mosh Teitelbaum
> evoch, LLC
> Tel: (301) 942-5378
> Fax: (301) 933-3651
> Email: [EMAIL PROTECTED]
> WWW: http://www.evoch.com/
>
>
> > -Original Message-
> > From: Mosh Teitelbaum [mailto:[EMAIL PROTECTED]
> > Sent: Wedne
EMAIL PROTECTED]
WWW: http://www.evoch.com/
> -Original Message-
> From: Mosh Teitelbaum [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 19, 2003 2:48 PM
> To: CF-Talk
> Subject: RE: Large Recordset Display Problem
>
>
> Couldn't be simpler...
>
>
Couldn't be simpler...
http://www.evoch.com/
> -Original Message-
> From: admin [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 19, 2003 2:40 PM
> To: CF-Talk
> Subject: Re: Large Recordset Display Problem
>
>
> Thanks all of you for the great
;
> tia
>
> Richard
> - Original Message -
> From: "Mosh Teitelbaum" <[EMAIL PROTECTED]>
> To: "CF-Talk" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 19, 2003 11:11 AM
> Subject: RE: Large Recordset Display Problem
>
>
> > Richard:
t; <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, March 19, 2003 11:11 AM
Subject: RE: Large Recordset Display Problem
> Richard:
>
> There are two steps involved in doing this, data retrieval and data
display.
>
> On the retrieval side,
Richard:
There are two steps involved in doing this, data retrieval and data display.
On the retrieval side, as others have mentioned, you'd be well served
caching the results of the query. If the query is user-specific, cache it
in SESSION. If the query is not user-specific, you might try addi
> -Original Message-
> From: Clint [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 19, 2003 10:45 AM
> To: CF-Talk
> Subject: Re: Large Recordset Display Problem
>
>
> Try caching the query. That will keep it from hitting the database again.
>
> Clint
>
> --
You could also put the entire result set into a group of blocks and
let the user page through them using visibility parameters - then you
wouldn't have to re-load the page.
- Jim
-Original Message-
From: admin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 12:36 PM
To: CF-Talk
Try caching the query. That will keep it from hitting the database again.
Clint
- Original Message -
From: "admin" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, March 19, 2003 12:35 PM
Subject: Large Recordset Display Problem
> I have a query that returns the re
10 matches
Mail list logo
