Re: Re: odbc going nuts

I'd recmmend you use the $_POST vars as this is more secure pete George Pitcher wrote:

Pete, Thanks for the tip. I do use $_REQUEST[] and then convert to variables. I moved my code to another machine and it was OK, so I've narrowed it down to a MS upgrade! Obviously tinkered with something. George

-----Original Message----- From: Pete Morganic [mailto:pete@daffodil.uk.com] Sent: 04 July 2003 1:56 pm To: php-db@lists.php.net Subject: [PHP-DB] Re: odbc going nuts Are registed globals off, otherwise u name to change $username to $_POST['username']

Any suggestions (apart from dropping Access in favour of another db -

client choice) Oh dear.. Access is a real pain in the butt and we now NEVER deal with a client that selects Access. Never had any complaints since. suggestions - mysql - postgresql - Firebird ... Pete George Pitcher wrote:

Hi all, Just finishing off a site using odbc and Access and it's thrown

up a problem

that wasn't there yesterday. I have a simple login with a username and password. If either

are blank, the

user gets bumped to the login page. otherwise the user table is

searched for

the username and password. my code looks like: $strSQL = "select * from user where (Username='$username' and Paswd='$paswd')"; I have an error script that kicks in if the query fails, and prints the query to screen. I've pasted the query straight into Access' SQL query window and it worked fine. I just can't see anything wrong with the code, or anything else. Any suggestions (apart from dropping Access in favour of

another db - client

choice) Cheers George in Oxford

-- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php