Question regarding endless -- browser keeps spinning and won't stop

I have a PHP file that is executed in a hidden frame. For some reason
the Web browser is endlessly running (the indicator at the bottom
hangs at about 50%)... the procedures in the code execute, but I can't
get the browser to stop.

I've read things here and there about this anomaly -- is there a
sprinkle of code I add in there somewhere to kill the browser to
workaround this? Anyone know what is going on here?

"Matthew" <mattsimc@yahoo.com> wrote in message
news:199e3613.0401100759.4a5d27bf@posting.google.c om...
> I have a PHP file that is executed in a hidden frame. For some reason
> the Web browser is endlessly running (the indicator at the bottom
> hangs at about 50%)... the procedures in the code execute, but I can't
> get the browser to stop.
>
> I've read things here and there about this anomaly -- is there a
> sprinkle of code I add in there somewhere to kill the browser to
> workaround this? Anyone know what is going on here?

I have seen wierd things like this before..
In one case, I wasn't printing my ending tags.

</body>
</html>

Matthew wrote:
> I have a PHP file that is executed in a hidden frame. For some reason
> the Web browser is endlessly running (the indicator at the bottom
> hangs at about 50%)... the procedures in the code execute, but I can't
> get the browser to stop.
>
> I've read things here and there about this anomaly -- is there a
> sprinkle of code I add in there somewhere to kill the browser to
> workaround this? Anyone know what is going on here?

Although there might possible be a quick-&-dirty trick to simply kill the
hidden frame I'd suggest you try and find out WHY the script causes this
behaviour. Maybe you have a clue as to which part of the script might be
responsible for this and post that snippet here for others to comment on!

jan


--
Today's tip : Get all your peer-2-peer appz&stuff from www.shareall.tk

Sorry, I should have been more specific -- this anomaly is occurring
when a database query is executed on this frame. I can't kill the
frame because I need it there to pull data from it. Any ideas on how
to stop this activity?

> Although there might possible be a quick-&-dirty trick to simply kill the
> hidden frame I'd suggest you try and find out WHY the script causes this
> behaviour. Maybe you have a clue as to which part of the script might be
> responsible for this and post that snippet here for others to comment on!
>
> jan