Hi,

We're currently changing the location of the data source for a bunch of CR
using VS.NET 03. For most stored procedures invoked by the reports, the
change in data source goes without any change to the field mapping.

We have a few stored procedures in reports that the Crystal plug-in is
unable to map the fields from the current data source to the new one (SQL
Server ODBC connections). The field names haven't changed, nor have their
data types.

It brings up the "Map Fields" dialog, but the upper-right quadrant, where
the destination stored procedure is located, has no parameters listed under
the procedure name. I've verified that the procedure executes fine.

Anyone encounter this before?

thanks,

Gene