It looks like the table you are exporting does not have an email column attributed to it while the new table has an email column. Are you adding the info by 'hand' for email into the second table or have you missed a column in your export?
If the table you are exporting doesn't have an email column and you plan on adding that data in later then drop the email column from the new table and add it in place later after you have imported the data. You can tell the column explicitly where it should be inserted in your alter statement.
ALTER table PN ADD email varchar(100) AFTER pn_uname;
Well the missing email column was something I overlooked.
I hadn't actually put the 2 queries together to run back-to-back; I was trying to simplify things and do each step individually, so the extraction went ok, it was 'putting' the data somewhere else that was causing problems - only I wasn't actually putting data anywhere just trying to put the statement together..that's where I went wrong, because from the import statement below I'm trying to put `pn_uid` , `pn_name` etc as the data instead of my intention of 'where the data should go' and than assign data with VALUE. oops
Your reference to dropping the email column helped me realize what I was doing wrong, because from you were mentioned how to manipulate the columns.
Here's how it should be:
`nuke_users` ( `pn_uid` , `pn_name` , `pn_uname` , `pn_email` , `pn_url` , `pn_user_avatar` , `pn_user_regdate` , `pn_user_icq` , `pn_user_from` , `pn_user_sig` , `pn_user_aim` , `pn_user_yim` , `pn_user_msnm` , `pn_bio` )