AS Richard has said, 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?
Doing that through your whole app may fix the problem as well, but if it doesn;t then move to the next serious mistake you are making: exception swallowing.
Your code does this:
Try
For i = 0 To ds.Tables(0).Rows.Count - 1
...
Next
Catch
End Try
So if anything goes wrong inside the loop, you throw away any error information and exit. That means that you don't know what went wrong, and have no way to find out!
That's called "Swallowing an Exception" and it's easy to fix: Use
Catch
with an exception parameter.
Try...Catch...Finally statement - Visual Basic | Microsoft Learn[
^] shows you how.
Now run your code in the debugger and if any exception occurs you can look at the details in the Catch block by putting a breakpoint on it. Those will tell you what happened, and where - which is the first part of trying to fix it!