Re: Re: catch the error

Boyd, Todd M. wrote: > Jesus Christ... everyone on this list must've had a long week, because > you guys are going blind. :D > > In examples sent to you, people foolishly replaced your $db var with > $db_connect ONLY FOR PART OF THE SCRIPT. You've defined your database > connection as $db_connect in some versions of the source, but then you > reference $db (without _connect) in your mysql_select call in that same > source. > > $db = mysql_connect([option list here]); # <-- this code instantiates a > connection > mysql_select_db([some name], $db); # notice how $db is here? > $result = mysql_query([some query], $db); # it's here, too! > > $db becomes your resource link when you use mysql_connect. That resource > link must then be passed to your mysql functions. Otherwise, they have > no idea which database connection you are attempting to use. > > # BAD: > $db = mysql_connect([options]); > $result = mysql_query([some query], $db_connect); # what's $db_connect? > who knows! > > # GOOD: > $db = mysql_connect([options]); > $result = mysql_query([some query], $db); # same resource link from > mysql_connect > > See? > > HTH, > > > // Todd Yes, and I would also strongly urge (scream at) PJ, to turn on E_ALL error reporting in any script he has problems with. #1 you'll figure out the problem because the errors will tell you exactly what the problem is "undefined variable db_connect", etc... #2 if you can't figure it out, someone here can easily if you give the errors. Virtually every problem you've posted throws an error(s) that will tell you what the F*** is the problem! -- Thanks! -Shawn http://www.spidean.com