Although Garth's solution will work, it's a poor DB design to store comma delimited values in a single column of a database.
It duplicates information, wastes storage space, promotes errors, and makes the data very hard to work with later.
For example, if the course "Basic" needs to be renamed to "Visual Basic" later on, you would need to change it in every row, and be extremely careful not to affect "Basic Maths" when you do it.
Worse, when you need to change a course for an individual - he swaps from "Visual Basic" to "C#" for example - it's horribly complicated to do in SQL because it's string handlking is marginal at best.
Instead, you should be setting up two tables:
Courses
ID INT, IDENTITY
Name NVARCHAR
And
CoursesTaken
ID INT, IDENTITY
UserID INT, Form.ID
CourseID INT, foreign key to Courses.ID
Then SQL can do what it does best - process relationships between data - and you use JOIN when you want to retrieve the data.
It makes all processing easier, and only complicates the original INSERT operation a little.