CREATE TABLE person 
(
FirstName varchar(15),
LastName varchar(15),
Age int
)

When I take 'Age int' out of that it fails to create the table. Why does it require that to be there?

It should be like this

CREATE TABLE `person` (
`FirstName` VARCHAR( 15 ) NOT NULL ,
`LastName` VARCHAR( 15 ) NOT NULL
) TYPE = MYISAM ;

Arez, did you simply took of the line, but let the comma on the preceding line ?
This could be the problem.
Otherwise, your query was semantically right, although I'd add an numeric field as a primary key.
Indexes on numeric fields are far more efficient than on varchar fields.

You can use an auto_increment option on the field, to let it increment on every insert, or use a sequence (depending the DB you're using)

create table person(
  personId int not null auto_increment,
  firstName varchar(255),
  lastName varchar(255),

  primary key (personId)
);

Yeah that's what I did and thanks for help!

For the record, are we talking about MySQL or SQL Server? The syntax in the first post looks like MS, and the first reply is definitely not MS convention.

Anyway, you got the answer, but here's a tip:

It isn't strictly necessary to have a primary key in a table. But there are very, VERY few situations where it really makes sense not to. If a table is going to be used as a log and only ever queried for sums and averages, and you know you're only feeding unique data, you don't need a PK. But if you ever need to update, delete, or select a single row, you need a way to identify that row out of all of what's in your table.

For your person table, you could make firstName + lastName the primary key. I think Tripy recommended an int because they're much faster to compare, and more efficient to index. When you need a foreign key in other tables, an int value makes a great deal more sense than two string values.

But you may want to add a unique constraint to the table to make sure that Forrest Croce isn't allowed two entries. You may not; there actually is another guy who shares my name. It probably depends on the scope of your application. But that's something to consider.

I couldn't follow most of that, but at least I understood the last part!!!one1