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

Error 13 Type Mismatch

P: 2

I am new to this group and new to VB6.

I have an ASP page which currently calls down to the DB three times to get information. I have been given the task of writing an SP which amalgamates the three previous SP's so that only one call is made.

Having written this new SP I executed it in SQL Server management studio and it returned the information I wanted.

However, when I altered the page to make just one call to this new SP it is returning nothing, just the Err.Number 13 and the Err.Description Type Mismatch. I am passing it 4 input parameters and one output parameter (all are integers). I am not able to debug the code at the moment due to network difficulties but if anyone can think of a possible reason for this I can investigate them once the network is back up.

Any help would be much appreciated.
Jan 11 '08 #1
Share this Question
Share on Google+
3 Replies

Expert 5K+
P: 8,127
It is really difficult to predict anything / what is wrong with your code.
Can you kindly post your code for reference of out experts please.
Jan 11 '08 #2

Expert 5K+
P: 8,434
Yes, more info required I think.

In the meantime, can you double-check that all fields are in fact defined as numeric in the database? Any that aren't will require delimiters (probably single quotes) around them.

Also, check that you haven't left out a space or something when concatenating everything.

Another possibility - could one of your search values be null or something?
Jan 11 '08 #3

P: 2
Hi guys,

I found the problem: the new SP was calling 2 other Sp's internally and filling a couple of temp tables. I then joined these tables to a view to populate a third temp table, then returned this table. The problem was, I didn't set NOCOUNT ON in the new SP, so it was trying to return all 4 select statements. It had nothing to do with the code or ASP page.

Sorry about that.
Jan 11 '08 #4

Post your reply

Sign in to post your reply or Sign up for a free account.