September 2003 - Posts
Just saw this exception for the first time
"An SqlParameter with ParameterName 'indate' is not contained by this SqlParameterCollection."
OK MS, this should read
"A SqlParameter with ParameterName 'indate' is not contained by this SqlParameterCollection."
I saw a blog on this recently, but I cannot find it now. Can someone refer me to the blog, or, in your best laymen words, give me a paragraph or two on how you describe .NET to your clients? This is to a client who is not technical.
I am a blogger: http://dotnetrocks.blogspot.com/
It seems most our our woes with DataBinding and updates\inserts have been related to ReadOnly elements in our schema.
I saw this during Update testing and just now saw it during Insert testing. In one case, our sproc returns a calculated field that stores T or F (true or false):
CASE WHEN n.faddr = '######' THEN 'false'
<xs:element name="MailStopEnabled" msdata:ReadOnly="true" minOccurs="0">
We databind one of our textbox control's enabled property to this. Well, it seems calling AddNew fails when we do this.
The new row is created, however you can never set the Position to that new row. As soon as I remove the binding to the calculated field, calls to AddNew work. By work I mean all of the controls are cleared out, a new row is created and the client is positioned to that new row.
My question is, if I want the proc to continue to build this field and we want to continue to bind to it, are there anyways to:
1- turn off the ReadOnly on this element
2- somehow work around this
We do not need to update or do an insert on this field. In fact, the field does not even exist in our database. We were simply trying to come up with a slick way to disabled this textbox when a certain condition is met the the sql query.
So, what I think I am seeing is inserts and updates for databinding will not work if you are using calculated fields from sql server or otherwise setting a ReadOnly attribute on your element in the schema.
He is not an ASPNetWebBlogger, however lets welcome Michael Richardson to the blogging community:
"I am where I am because of this man"
So, we have a handful of files in our project that we do not want to check into VSS. We see this pretty little red check next to them stating 'Newly Added File' and, every time we do a project check in, we have to make sure we unselect these files.
To disassociate these files with VSS, we did:
File > Source Control > Exclude (filename) From Source Control
And now we are good. Many thanks to Ivan Towlson at White Carbon for the tip!
Thanks for the overwhelming replies! Wow, never knew there were so many .Netters in the area.
We are quickly trying to put this together and make it happen. Are there any folks, perhaps through INETA, who would like to be guest speakers? I am sure the group will get quickly bored with Mike, Brady, Bill and I speaking every month!
BTW, Mike Richardson is heading up the effort. Check out his blog:
So it seems this bastard infected my machine sometime on Monday. I spent most of the day yesterday pulling out my hair and deleting fake Microsoft e-mails.
Go to this link for details on the virus:
We are in the process of starting a .NET Users Group in Richmond, VA. All those interested, send me an e-mail and we will get you on our distribution list.
Has anyone else done this yet? We are using DataSet\DataTable types throughout our application. We would like to add a couple of custom methods to DataTable. Looking over the docs, I do not see any reason why we cannot do this. However, prior to writing all the code and implementing this only to discover a great reason why we should not, I'd like to hear from anyone who has done this or can tell me why we should not do it.
More Posts Next page »