Question
dbvarname NOT ignored completely in CF8
While dbvarname is supposedly ignored in CF8, we have
experienced an error thrown on proc calls that have dbvarname
specified for the IN parameters, but not the OUT parameters. This
code works fine in CF7.
We are trying to put a CF8 migration plan in place, and this could be the show-stopper for us. Our codebase is huge, with hundreds if not thousands of proc calls, most of which do not have dbvarname specified for the OUT parameters.
Is there a way to stop the hard-error that results in these cases? A configuration setting somewhere? We are on a time-table for migration to support our next release in March 2008.
We are trying to put a CF8 migration plan in place, and this could be the show-stopper for us. Our codebase is huge, with hundreds if not thousands of proc calls, most of which do not have dbvarname specified for the OUT parameters.
Is there a way to stop the hard-error that results in these cases? A configuration setting somewhere? We are on a time-table for migration to support our next release in March 2008.