Thanks for the guidance guys... Going on the idea that it was indeed a problem with script, arrays, etc., I found a few things. The display was well over 9000 characters before it failed, so that 8k max thing was unlikely in this case. But it seems to have been fixed by other things done. They all happened at more or less the same time so not sure which was the culprit.
The first had to do with session_bug_compat_42. The ini is supposed to allow the error message to be shut off but doesn't. I started to get that error so the only way to eliminate it was to find the reason. It turned out it was an empty table that caused it. The next was a field name typo in an input query. Third, another table was corrupt to the point of being 'occupied', when looked at with phpMyAdmin. Even so, my program had seemed to run fine otherwise. All in all, I'm happy for finding all these things. We all should have more difficulties, eh? It would do us good. <g> Just kidding. I have not yet tried too hard to reintroduce the problem. If I take the time or have other news, I'll be sure to post it. Thanks again. Floyd On Fri, 30 May 2003 21:02:05 -0400, you wrote: >Well, I don't know if this might be it, but a while back, I had problems >with apache + php (forget which version) and a bug in php that cause memory >problems. > >I was using an array to store fairly large amounts of data. What would >happen is something similar to what you describe. Modifying the code to >avoid using an array solved the problem. Have not had the problem since >upgrading php. > >Martin > >Floyd Baker <[EMAIL PROTECTED]> wrote in message >news:[EMAIL PROTECTED] >> >> Hello... >> >> I have a routine that works fine on local win98 but when it runs on >> linux online, the screen output is cut short. I have lengthened the >> 30 second script time max to 45 but that made no difference at all. >> >> Depending on the particulars, the routine stops at a certain spot. If >> it is rerun, it stops at the very same spot again. Putting in other >> particulars cause it to stop at a different point, further down. It >> seems that changes which affect the number of mysql calculations, make >> some difference in the length of the screen display, but it's only a >> minor amount. It cuts off somewhere around 4 pages. >> >> Any ideas please. >> >> Floyd >> >> -- -- -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
