On a more awake inspection, a few things occur:
1) The syntax of an INSERT command doesn't contain the SET keyword and requires parentheses: SQL INSERT INTO Statement
2) Always list the fields you are INSERTing into: if you don't then SQL assumes "left to right" order for the columns - and since many tables contain an IDENTITY of UNIQUEIDENTIFER column at the start your new data will try to set that and fail. Listing the columns makes your code more robust and able to handle DB changes without your code needing to be modified.
3) Don't do it like that! Never concatenate strings to build a SQL command. It leaves you wide open to accidental or deliberate SQL Injection attack which can destroy your entire database. Always use Parameterized queries instead.
When you concatenate strings, you cause problems because SQL receives commands like:
SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'
The quote the user added terminates the string as far as SQL is concerned and you get problems. But it could be worse. If I come along and type this instead: "x';DROP TABLE MyTable;--" Then SQL receives a very different command:
SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;
Which SQL sees as three separate commands:
SELECT * FROM MyTable WHERE StreetAddress = 'x';
A perfectly valid SELECT
DROP TABLE MyTable;
A perfectly valid "delete the table" command
And everything else is a comment.
So it does: selects any matching rows, deletes the table from the DB, and ignores anything else.
So ALWAYS use parameterized queries! Or be prepared to restore your DB from backup frequently. You do take backups regularly, don't you?