|
Posted by ClothingStore on February 15, 2007, 2:49 pm
Please log in for more thread options Glenn, you are awesome, thank you. It did the trick and works great. I
appreciate all that you do on this site and the questions you answer. It's
great.
"Glenn Adams [MVP - Retail Mgmt]" wrote:
> Try adding the following line to the beginning of your SP:
>
> SET NOCOUNT ON
>
> This suppresses the "Rows affected" message that your insert is sending
> back...
>
> The SP is all within SQL Server, it really has nothing to do with RMS
> specifically.
>
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@tibercreek.com
> ----------------------------------------------
> Please DO NOT respond to me directly but post all responses here in the
> newsgroup so that all can share the information.
>
>
> ClothingStore wrote:
> > Is there any examples of writing stored procs directly in RMS? For example
I
> > have a stored procedure I have written that gets fired off from CR8.5. The
> > stored proc has one section that does an insert into a temp table and at the
> > end of the stored proc does a select of the temp table. Any time within the
> > stored proc when doing an insert the last select does not work. If I do not
> > do an insert within the stored proc everything works as normal. I even
tried
> > having my stored proc call another stored proc when it gets done, but
because
> > of that insert it has problems. Is there anything written anywhere or
> > documented about some of the issues with stored proc writing directly into
> > RMS?
> > Thanks
>
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap