Problems getting 200 SPs to work in 2005...

All,
Appreciate any help in advance. I have a developer working for me who
is a pretty well-seasoned fellow. He's trying to get some scripts that
take advantage of some SPs written for SQL Server 2000 to run on 2005.
He's getting an error saying the wrong number of arguments is being
passed. He looks through the code but it looks perfectly fine.
Tracing it yields nothing either.
Any ideas? We're in a crunch (like no one else is right?) and need a
quick answer. Do we have to revert back to 2000? Or are we missing
something? Thanks.
HNM
I assume your developer is calling stored procedures and getting errors
like:
Procedure 'MyProc' expects parameter '@.MyParam', which was not supplied.
or
Procedure or function 'MyProc' has too many arguments specified.
Assuming these are user stored procedures, I wouldn't expect either of these
errors to be directly related to SQL 2000 vs. 2005. Perhaps your developer
can post a relevant code snippet so someone can help.
Hope this helps.
Dan Guzman
SQL Server MVP
"HNM74" <hnmcclain@.gmail.com> wrote in message
news:1144112777.882783.182980@.g10g2000cwb.googlegr oups.com...
> All,
> Appreciate any help in advance. I have a developer working for me who
> is a pretty well-seasoned fellow. He's trying to get some scripts that
> take advantage of some SPs written for SQL Server 2000 to run on 2005.
> He's getting an error saying the wrong number of arguments is being
> passed. He looks through the code but it looks perfectly fine.
> Tracing it yields nothing either.
> Any ideas? We're in a crunch (like no one else is right?) and need a
> quick answer. Do we have to revert back to 2000? Or are we missing
> something? Thanks.
> HNM
>
|||Hi
You don't say if you have recompiled the code in 2005 or just upgraded the
database.
John
"HNM74" wrote:

> All,
> Appreciate any help in advance. I have a developer working for me who
> is a pretty well-seasoned fellow. He's trying to get some scripts that
> take advantage of some SPs written for SQL Server 2000 to run on 2005.
> He's getting an error saying the wrong number of arguments is being
> passed. He looks through the code but it looks perfectly fine.
> Tracing it yields nothing either.
> Any ideas? We're in a crunch (like no one else is right?) and need a
> quick answer. Do we have to revert back to 2000? Or are we missing
> something? Thanks.
> HNM
>