with query output (but is cached too). For some reason (sometimes) IE
would report that a menu element was not defined, though it appeared to
be. I was trying to inject a wait time to see if this was the problem
(maybe timing?). In the course of doing this using some code I found
the error went away. It turns out for some reason that if I put a
cfflush tag above the menu creation that the error would go away. I
still don't know why this is the case, nor what created the ephemeral
error in the first place.
Thanks very much for clearing up my misunderstanding,
John
Want information on Hikes in Western Washington?
http://www.attrition.ws Check it out!
________________________________
From: Philip Arnold [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 25, 2004 10:11 AM
To: CF-Talk
Subject: RE: Questin about cflush
> From: John Munyan
>
> Can anyone tell me what the effect cfflush would have on
> subsequent cached queries is? I don't want to flush
> subsequent cached queries and it looks like they are not
> being flushed (which is good). Is this the correct
> interpretation?
Apples and Oranges
CFFlush is nothing to do with queries, but to do with sending content to
the browser
>From the documentation:
The first occurrence of this tag on a page sends back the HTML headers
and any other available HTML. Subsequent cfflush tags on the page send
only the output that was generated after the previous flush.
________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
