The first column is my primary key (customer article number). I only get the lines back when I'm looking for the article number with only number in it. In this example I get 11111:TEST:TEST:TEST:TEST. The others cause an error Unknown column 'XZ14B' in where clause. But I don't give the article numbers to the column scalar. In the column scalar is really the column name (in this case tab1).
Did I make a mistake at the columns values. First column is CHAR(30) or VARCHAR(30) right ?
Crosspost: http://forums.mysql.com/read.php?10,558320,558320#msg-558320

In SQL, you need to quote strings, otherwise they'll be interpreted as column names and such. That's what the warning is trying to tell you. I see you're trying to properly quote the table name and column, but you're failing to quote the value. Try the quote() method.

Frequently, you'll find that using placeholders will give you more robust code, so you may want to learn to use them. It's certainly no harder than building the SQL strings yourself, and less likely to fail. The only problem in this case is that you can't pass in an identifier (at least for the databases I typically use).

Hello roboticus,
I can't find the site at the moment, but I had read that the the columns always need to be quoted to identify them als columns from mysql, and the values not ?
Couldn't it be that my primary key has a problem ? Because all numbers without letters are taken.

No, that's backwards. In SQL (at least in MySQL), you need to quote string values, not column names. A statement like this:

SELECT * FROM mytable WHERE customer = Smith;

tries to find rows where the value of the customer field equals the value of the Smith field. So it gives you an error like the one you got, complaining that there isn't a column named Smith. If you're looking for a customer whose name is Smith, you do:

SELECT * FROM mytable WHERE customer = 'Smith';

In Perl/DBI, you can do that a couple different ways. The second one below, using placeholders, is much safer, especially when searching on user-provided data (which is the case most of the time). It's also easier, because you let DBI do the quoting for you.