Hi,

As already identified by the two previous posters

1) You need to have an insert statement preceeding each row you wish to insert into the table.

2) Having varchar columns specified as max is unneccesary as you should be able to specify an acceptable length.

3) SQL Server is unable to convert the char data to the money which is a numeric type. e.g. the three characters of each example have either "/yr" or "/hr" which SQL Server is interpreting as being a string whihc it can't implicitly convert.

In addition I would suggest the following.

A) The salary column seems to be used to hold different types of information. e.g for most entries it appears to be holding an hourly rate, but for one example it holds a yearly salary. I would suggest introducing a new column called SalaryType and use this to record if the Salary is an hourly rate or a yearly salary. This would allow you to retain the rate type information.

B) I would also suggest changing the age column to hold the actual date of birth of the individual, the actual age could then simply be calculated. If you only hold the actual age it would be incorrect once the persons next birthday passes.

Hope this helps.

Angus