I've seen/used that kind of SQL statement many times, so it should work fine... I suspect that the issue is to do with Reserved Words, as implied by the error message.

The list of words that are reserved depends on the technology you are using (each has their own), and they can be found in this FAQ article.

To correct the issue it is best to rename the fields, however you can surround the field names in the SQL statement with square brackets instead, eg:
Code:
SELECT BannedMembers.[BanDate], BannedMembers.[BanReason], ...