Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / ADO.NET / June 2004

Tip: Looking for answers? Try searching our database.

OleDbParameter - Maybe not a bug... but it still sucks!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
spamfurnace - 14 Jun 2004 12:01 GMT
Howdy,

Can someone please explain the rational of letting an OleDbCommand take more
parameters than the query string is expecting. If i have 3, ???, in an
Access Query string, and i supply 4 parameters, it DOESN'T fall over/throw
an exception? Whats the benefit to the developer of this behaviour?

Ive just wasted 45 bloody minutes dicking around with this? O.k so i should
have looked a little closer... and it's probably my own damn fault for using
dirty old A2K as a datastore, but the query actually had 21 paramters and i
only supplied 20 ?.

I'd much rather it fail, than pass through the values all out of order....
because it still allows an invalid method to return true. This behaviour is
a bunch of arse.

:(

What an incredibly dull reason for the error. I was expecting something a
little more FANTASTIC!

TIA
Richard
Paul Clement - 14 Jun 2004 19:11 GMT
¤ Howdy,
¤
¤ Can someone please explain the rational of letting an OleDbCommand take more
¤ parameters than the query string is expecting. If i have 3, ???, in an
¤ Access Query string, and i supply 4 parameters, it DOESN'T fall over/throw
¤ an exception? Whats the benefit to the developer of this behaviour?
¤
¤ Ive just wasted 45 bloody minutes dicking around with this? O.k so i should
¤ have looked a little closer... and it's probably my own damn fault for using
¤ dirty old A2K as a datastore, but the query actually had 21 paramters and i
¤ only supplied 20 ?.
¤
¤ I'd much rather it fail, than pass through the values all out of order....
¤ because it still allows an invalid method to return true. This behaviour is
¤ a bunch of arse.
¤
¤ :(
¤
¤  What an incredibly dull reason for the error. I was expecting something a
¤ little more FANTASTIC!

Don't believe the Jet database engine will attempt to resolve parameters not defined in the query.
Any extra you supply via the provider are simply ignored.

Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.