in reply to Let's try this again. Script pulling mysterious blank row.

If you also use warnings, you will get a warning about use of uninitialized values in concatenation if @Quote comes back undefined, which has already been suggested (more than once) as a possible cause of your problems.

Another avenue you could try would be to also select your table's primary key and print that first. Since it's a primary key, you know it's populated in every record; if it comes up blank, then the database isn't giving you a record. If it displays only the key, then you know exactly which record is having problems, since the primary key uniquely identifies each record. And printing it first safeguards you against any possible unfriendly data in other fields somehow hiding it (assuming it's a typical autonumber-type key rather than a text string).