I thought the same thing at first. I just found out the problem. The stored procedure in question lives in a different database than the database the datasource points to (there is a long explanation as to why we have it that way). Anyway, we are using User-Defined Datatypes and the proc was using a user-defined datatype that was not defined in the default database. It seems that CFMX is using the metadata from the default database in the driver instead of the database that the cfstoredproc tag references.
>Alisa, > >Is this the only proc not working? I'd be curious to see if other >stored procedures that dont use CF_SQL_TIMESTAMP would execute. > >-Adam > > >On Tue, 01 Feb 2005 13:53:49 -0400, Alisa Thomson <[EMAIL PROTECTED]> wrote: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192694 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
