Sounds to me like you need to go out and hire a PHP programmer to go through your code and get your site back up and running. Then that same person can give someone in your organization some tutorials on how to maintain your code so that this sort of thing does not continue to happen. <?php /* Stephen Johnson c|eh The Lone Coder http://www.thelonecoder.com stephen@xxxxxxxxxxxxxxxx 562.924.4454 (office) 562.924.4075 (fax) continuing the struggle against bad code */ ?> > From: "Matt M." <h.dudeness@xxxxxxxxx> > Reply-To: "Matt M." <h.dudeness@xxxxxxxxx> > Date: Fri, 18 Feb 2005 11:18:23 -0600 > To: "George A. Balanos" <gbalanos@xxxxxxxxxxxxxx>, PHP general > <php-general@xxxxxxxxxxxxx> > Subject: Re: FATAL: emalloc() > > On Fri, 18 Feb 2005 12:10:32 -0500 (GMT-05:00), George A. Balanos > <gbalanos@xxxxxxxxxxxxxx> wrote: >> Thank you Matt, I found that also but to be honest the person who built this >> server recently passed away. He was our php specialist and to be honest I >> have no clue on how to activate this change. I have someone that knows Linux >> but after that we have no idea how to go about this change, can you point me >> in the right direction where I can learn to do this change or if you know a >> good write up on how to execute this? > > > > reply to the whole list. You get more answers that way > usually you would execute it something like this > odbc_exec ( $db, 'set textsize 9999;'); > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
