I'm trying to install a script i used over a year ago. I have ran into an error problem that i can't seem to figure out.

I get this error when i visit index

I'm thinking it has to do with the php coding/design we have because the database works with original design. Any help would be great , Thanks

I'd hazard a guess that you have an error in your SQL near out)

but without seeing the sql itself that you are sending to the sql engine its a
leetle tricky to diagnose

Do you want me to post up something? I dont know much about mysql , so im not sure what they mean by that.

The error says its under table traffic , no idea if this is any help or not.
http://img31.imageshack.us/img31/2180/mysqlv.jpg

IN and OUT are reserved words and should not be used as column names

DATE isn't reserved (in mysql) but you shouldn't use it either

I didnt write the code , i would change it but it probably will mess up something at the site. Is that what the error is?

looks likely
there is a workaround if you have used reserved words and that is to prefix with the table name or encapsualte in quote marks
eg
select mytable.reservedword from mytable
or
select 'reservedword' from mytable

but its nasty.

Does MySQL really allow to quote reserved words with single quotes?

I thought it's either the backtick:

select `reservedword` from mytable

or (when running in ANSI compatible mode) with double quotes:

select "reservedword" from mytable

of course not!!

healdem was working without his glasses again, and simply mistook the backticks as quote marks

instead of this, which is wrong --

SELECT id, 'in', 'out' FROM hl_listing

you need to write it like this --

SELECT id, `in`, `out` FROM hl_listing

you may well be right on that score, I've never had need to use it so I dunno, but maybe the quoted page from the MySQL manual will reveal all....

They are allowing double quotes for character literals, so it wouldn't have surprised me if they got this wrong way round as well

This doesn't make sense though , because this database works fine on the original design. We only get this error when using it with our design.

My partner tried changing the names and the code so it would work. Didn't work. Either that or he didnt do it right.

I vote for the latter.

And since you are coming looking for help, you need to post more than "didn't work" to give us an idea.

show us the query and any error messages.