Check out this article by Jeff Prosise,
Keep Sites Running Smoothly By Avoiding These 10 Common ASP.NET Pitfalls
A must read !
Markdown Front Matter For Metadata
4 years ago
.Net, ASP.Net, C#, VB.net, SQL Server, Xml, CSS, Design Patterns related tips, tricks, code snippets, articles, links, thoughts, etc. from Binu & Subi Thayamkery.
.net etc.
Binu Thayamkery is a seasoned software architect with more than 13 years of experience in developing enterprise grade connected systems using Microsoft Technologies. In his current position as a lead consultant-solution architect with Prudential Financial, he is working on architecture of next generation investment reporting framework using .net 3.5/WCF/AJAX, etc. He holds a Masters Degree in Computer Science from Colorado State University. Subi Thayamkery is an experienced software developer with more than 8 years of developing various application software systems ranging from workflow automation systems to compliance management tools. She currently works as a technology consultant for Prudential Financial where she helps develop a new system for corportate governance department. She holds an Electrical Engineering degree from New Jersey Institute of Technology.
Tuesday, August 08, 2006
ADO.Net and Sybase ! Strange behavior !
This is what I see, may be there is something that I don't see !
I am using .Net v1.1, Sybase db ver 12.5 with Sybase ASE OleDb Provider Ver 2.70.
When I create parameters for my command (CommandType is StoredProcedure), it expects me to create the params in the same order as specified within the stored procedure. I am creating the params using names and not by ordinal! There is no error thrown even when the params are in different order, values simply gets assigned to the wrong params !!
Did any one of you have seen similar issue ??
I am using .Net v1.1, Sybase db ver 12.5 with Sybase ASE OleDb Provider Ver 2.70.
When I create parameters for my command (CommandType is StoredProcedure), it expects me to create the params in the same order as specified within the stored procedure. I am creating the params using names and not by ordinal! There is no error thrown even when the params are in different order, values simply gets assigned to the wrong params !!
Did any one of you have seen similar issue ??
Subscribe to:
Posts (Atom)
Place holder for some text here!