Thanks all, specifying the length of the field did it.
----- Original Message ----- From: "Clint" <[EMAIL PROTECTED]> > In your stored procedure you have to put the length of that column. > Otherwise SQL Server defaults it to a length of 1. > > Change that and rerun your stored procedure. Also, you can run this in SQL > Query analyzer and see what you get back. That way you can determine if it > is the procedure or CF that is causing the problem. > > HTH > Clint ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
