in short the db is not pulling the wrong months, its doing precisely what you have requested, based on your table/column design
how are you letting your users define month?
are you using number (3), abbreviation ("Mar") or full name ("March")
are you storing the date as sting (yuck) or as a date time value?
I'd suggest you restrict your users inputs by using a form which validates anythign sent to the SQL engine is legit, that means you can then comntrol what the users does, but it alos means that there is a consistent interface (it means for example that a user can rerun a report or a series of reports using the same date/month)
if you are storing a date as string (and your really really shouldn't) you can use the like construct
however it depends on how your dates are stored say they are stored in UK / Aus and other 'sensible countries where the month is the middle part of the date you could look for "*/01/*" to find January or "*/1/*"
conceivably you may have to do both, you may also have to look for "*Jan/*" AND "*January*"
if you use US dates
look for "* 1/" and "* 01/* and so on......
you will get yourself tied in knots if you persist in storing dates as sting values.
its far easier if they were stored as date time values
you'd just use where month(mydatecolumn)= mynumericvalue
(virtually) all sample code I post will almost certainly contain typos, some logic errors and will need debugging. its air code, providing with good intentions but no guarantees it works or is fit for purpose. in essence yer gets what yer pays for...
PS I'd rather be riding on the Tiger 800 or the Norton