OK, so I am doing something simple... adding a ControlParameter to a SQLDataSource. I just want to add it as an optional filter. The ControlParameter points to a TextBox. Like this...
<asp:ControlParameter ControlID="txtFiltCC" Name="TCity" PropertyName="Text" Type="String" DefaultValue=""/>
Not only does the result return nothing, according to the Microsoft SQL Server Profiler, the query is never even sent to the server!!!
What the HELL!?!?!?!?
I change the SelectCommand to not use the @TCity paramater and still... no query sent. The GridView bound to the SQLDataSource reports that no records were retrieved. Hmmm... makes sense since according to SQL Server Profiler, no query was sent.
Then I find the ConvertEmptyStringToNull property on the ControlParameter. It's default is 'True'. Hell, I don't want it to be null, so I change it to False. Friggin SHAZAM! The SQL query is sent and I get a result set. Why the HELL would the ConvertEmptyStringToNull cause a query to not be sent, especially if the parameter isn't even used in the query???? This works fine...
<asp:ControlParameter ControlID="txtFiltCC" Name="TCity" PropertyName="Text" Type="String" ConvertEmptyStringToNull="False" DefaultValue=""/>
Really, Microsoft... This is a crazy little piece in ASP.NET
So... For anyone scratching their head about a GridView not being populated from a SQLDataSource that is using a ControlParameter pointing to a TextBox, this just may be the solution.
No comments:
Post a Comment