yeah sometimes I have to put SET NOCOUNT ON in some stored procs too. I find some stored procs throw a wobbly in ASP as well as Dephi, but I suspect thats more of an ADO issue since I use ADO in both technologies. Jeremy
_____ From: [email protected] [mailto:[email protected]] On Behalf Of Leigh Wanstead Sent: 4 August 2009 14:50 To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] QuickReport Delphi 5 Enterprise MSSQL 2005 Storedprocedure I got around the problem by putting these statements in the stored procedure SET CONCAT_NULL_YIELDS_NULL on; SET ANSI_WARNINGS on; SET ANSI_PADDING on; SET ARITHABORT on; Have a nice day Regards Leigh -----Original Message----- From: [email protected] [mailto:[email protected]]on Behalf Of Jeremy Coulter Sent: Tuesday, 4 August 2009 2:30 p.m. To: 'NZ Borland Developers Group - Delphi List' Subject: Re: [DUG] QuickReport Delphi 5 Enterprise MSSQL 2005 Storedprocedure does the Stored proc. you are calling work ok if you call it in iSQL? That would help eliminate it being something wrong with the stored proc. Jeremy _____ From: [email protected] [mailto:[email protected]] On Behalf Of Leigh Wanstead Sent: 4 August 2009 14:26 To: NZ Borland Developers Group - Delphi List Subject: [DUG] QuickReport Delphi 5 Enterprise MSSQL 2005 Stored procedure Good afternoon, I am calling a stored procedure in Quick report Dataset. I got the error shown in the attachment. What can I do? TIA Regards Leigh
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
