You haven't yet realized it, but you just discovered SQL injection vulnerability in your code. Basically anyone who can run this code on the server can put malicious SQL inside your article and it will be executed.
This is what the error is trying to say in disguise: it interpreted the contents of your link/article and made them part of the SQL - which became syntactically incorrect. Don't try to escape the value socialButton
and articleText.Text
manually. Use named parameters instead:
insert into myArticleTable (articleText) values (?)
And populate this parameter with something like this:
cmd.Parameters.AddWithValue("parm1", socialButton + articleText.Text);
Remember, never generate SQL manually by concatenating strings. Moreover, named parameters are much cleaner.
Disclaimer: I am not a .NET developer, copied code snippet from How to parameterize complex OleDB queries? and how to update a table using oledb parameters? But the same rules apply in virtually every language.