By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,640 Members | 2,279 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,640 IT Pros & Developers. It's quick & easy.

Help with Input string was not in a correct format

P: n/a
I thin i have found the most frustrating error EVER

"Input string was not in a correct format."

We are using Custom Datasets,,, so when it comes to running a stored proc
you set all the values and check they are OK>.

then when you actually run
myCommand.ExecuteNonQuery();

It throws that stupid error...

Even with running SQL profiler wont help as the code hasnt even hit the
datbase as yet.

Can anyone suggest a good way to debug these problems other than doing one
stored proc param at a time#?
Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
H

Is it possible for you to show us the code that is used to build up your
command object

Looking at the code we can suggest an solution

Kashyp
Aztec Software and Technology Service Ltd
Bangalore
Nov 18 '05 #2

P: n/a
Bascially this is when a string cannot be converted to the approrpriate type
(for exemple convering "ab" to an int should give this error).
I would double check the sp parameters. Post more info if needed...

"Darren Clark" <dc******@hotmail.com> a écrit dans le message de
news:mV******************@news-server.bigpond.net.au...
I thin i have found the most frustrating error EVER

"Input string was not in a correct format."

We are using Custom Datasets,,, so when it comes to running a stored proc
you set all the values and check they are OK>.

then when you actually run
myCommand.ExecuteNonQuery();

It throws that stupid error...

Even with running SQL profiler wont help as the code hasnt even hit the
datbase as yet.

Can anyone suggest a good way to debug these problems other than doing one
stored proc param at a time#?

Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.