|
The problem, I think, is actually that the procedure is returning a 4S0 and SQL wants it to be packed. When I changed DEC to NUMERIC, the decimal data error went away. It did not, however, return the result I expected. It seems the first parameter value received by the service program contains nothing resembling what I passed. That might have something to do with having to use VARYING/VARCHAR parameters when the service program is expecting fixed length. I guess I'll need to experiment a bit more. Thanks everyone for getting me this far. I never would have made it without you. Donald R. Fisher, III Project Manager Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@xxxxxxxxxxxxx <clip> Your stored procedure has no return value. That's why you get the decimal data error on the return value. And I assume you'll never get returned your output parameters. <clip>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.