Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- From: Lars-Erik <lars-erik@xxxxxxxxxxxxxxxx>
- Date: Wed, 14 May 2008 06:58:00 -0700
Try explicitly naming the schema: "dbo.myprocedure" rather than simply
"myprocedure"
Thanks, I'll guide the customer through the change over the phone tomorrow.
Grasping at straws are all I'm hoping for now, to be honest. Unless one of
the SQL Server or ADO developers wanna have a dive in their code. :D
L-E
.
- References:
- Non initialized Cmd Parameter Collection via ASP vs SQL Server 200
- From: Lars-Erik
- RE: Non initialized Cmd Parameter Collection via ASP vs SQL Server 200
- From: Steven Cheng [MSFT]
- RE: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- From: Lars-Erik
- Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- From: Bob Barrows [MVP]
- Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- From: Lars-Erik
- Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- From: Bob Barrows [MVP]
- Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- From: Lars-Erik
- Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- From: Bob Barrows [MVP]
- Non initialized Cmd Parameter Collection via ASP vs SQL Server 200
- Prev by Date: Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- Next by Date: SqlParameter and DBNull.Value - possible bug?
- Previous by thread: Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- Next by thread: SqlParameter and DBNull.Value - possible bug?
- Index(es):
Relevant Pages
|
Loading