Second call of an SQL query throws a syntax error?

Question

Private Sub RefreshDataSet()
Dim strSQL As String = DataAdapter1.SelectCommand.CommandText
Try
DataSet1.Clear()
DataAdapter1.SelectCommand.CommandText() = Trim(strSQL & " WHERE BadgeID = " & strEmployeeBadge)
DataAdapter1.Fill(DataSet1)
Catch ex As Exception
MsgBox(ex.Message)
End Try
End Sub
When I call the above procedure, the sub does work correctly and I get the expected results / records in the dataset.  But, when I call the Sub again (to refresh the dataset) it gives me an "incorrect syntax" error.
I'm not sure why it is doing this.  Any suggestions or ideas?

Answer 1

Youjun,
It's very frustrating when you keep asking if the code is the same, or if I have tested the code.  I've said that I debugged.. I've said I have tested the code.  Your continuing to ask me this is pointless, rude, and only serves to make YOU look
stupid.  I'm sorry if that is rude, but please stop asking me!
To respond:
I supposed that the original DataAdapter1.SelectCommand.CommandText is "select * from table1"
-Yes, the base command is similar to this, except that I call each database field, not using the *.
1) When you run it the first time, the DataAdapter1.SelectCommand.CommandText will be "select * from table1 WHERE BadgeID ='123'".
-Yes, I append 'WHERE BadgeID = XXX' to the query, the first and
each subsequent time.  Again, I said that the code/call/syntax DOES NOT CHANGE.  It is the
same every time.
2) Then you changed the strEmployeeBadge, I supposed that is '234'
-NO!  I do NOT change the code!!  I'm sorry, but what part of 'the query is
exactly the same' is unclear?
3) when you run it next time, the DataAdapter1.SelectCommand.CommandText will change to "select * from table1 WHERE BadgeID ='123'
WHERE BadgeID = '234'"
-NO!  I have specifically tested for this
and as stated, the SQL syntax does not change!
So it 'syntax' fail will pop out when second call.
-NO, your assumptions are INCORRECT.
I suggest you recording the commandText when first change the DataAdapter1.
I write a testing program for you.
-Your 'testing program' is for all purposes, the same exact code as what I used.  There is no difference.  
Now, as also stated before, I have several other instances
where I use the same 'technique' to amend the base SQL queries of the DataAdapter.  Each of these other instances work fine, and I use them to 'refresh' my DataSet information several times throughout the running of my program.  Just for some
reason, this time, it does not work.  I don't know why and was hoping someone else had found the same/similar issue and also found a resolution.  The DataAdapter is configured the same as the others, the code is the same as well.  I will just
have to find a work around, or other way to do what I want I guess.
Lastly, yes, I set strSQL in the subroutine because I want that variable to be gone at the end of the procedure.  It recalls, then sets the syntax, every time the Sub is called on purpose.  I do not want strSQL to be 'global', which by the way,
according to Microsoft documentation I have read, is no longer possible.  Global variables are 'technically' not used/recognized anymore.  If this has changed, then I stand corrected.
Thank you for responding, I will just find another solution I guess.