Issue with VS project - Report has remapped fields

Question

VS 2005, Crystal XI R2
We recently upgraded a VS project using Crystal reports. The database has changed, with table name and field name changes.
We used the "set datasource location" to remap the table names and fields. Reports run fine as stand alone.
But when running from the VB project we have an issue when logon info is applied to the subreports.
In the standard code to apply logon information to the subreports, this line of code
Crtable.Location = crConnectionInfo.DatabaseName & ".dbo" + "." + crConnectionInfo.UserID + "." + crConnectionInfo.Password + "." + Crtable.Name
fails because Crtable.Name resolves to the old table name (ctct) which has been remapped to new table ca_contact using the set datasource location option from Crystal.
If I comment out this line of code, the reports seem to run fine, sometimes we get prompted for connection info. Once the info is set, the report runs.
But can I get this line of code to work? is there some way to get Crtable.name to point to the actual table name "ca_contact" and not the old name "ctct" that the table and fields were remapped from?

Answer 1

Thanks for the reply, but the subreport has been already remapped. I just went back in and double checked.
I am thinking about writing some code that will be something like
(pseudo)
if table = ctct then replace table name with ca_contact
but there should be a way around this. Even though the table is remapped, it is picking up the old table name alias instead of what it is mapped to.