SetDataSource Property is Changing my TableName

** Please Pardon if this duplicates.  It was posted last night and then appears missing this morning. **

I have a crystal report that uses two table adapters as inputs.  These inputs are intended to vary between client and need to be changed at runtime in VB.NET.  Using the "networked" code to ensure consistency, my code used to work just fine on my old PC (with XP Pro as operating system).  Since upgrading to a new PC (Windows 7 32 bit) and with no program changes, the code is no longer working.  It appears that the SetDataSource execution is changing the TableName.

Dim Name1 AsString, Name2 AsString, Name3 AsString, Name4 AsString, Name5 as String

Dim _db AsNewSqlDatabase(GetConnectionString(_dbName))

Dim ds AsDataSet = _db.ExecuteDataSet(CommandType.Text, "select * from LossData")

Dim oldDatabase AsNewSqlDatabase(GetConnectionString(_oldDbName))

Dim oldDs AsDataSet = oldDatabase.ExecuteDataSet(CommandType.Text, "select * from Test")

Dim cr AsNew CrystalDecisions.CrystalReports.Engine.ReportDocument

cr.Load(Path.Combine(My.Settings.ReportPath, "ClaimGroups.rpt"))

Name1 = cr.Database.Tables(0).Name              'RETURNS LossData AS Name1 (Name of first alias in ClaimGroups report)

Name2 = cr.Database.Tables(1).Name               'RETURNS OldLossData AS Name2 (Name of second alias in ClaimGroups report)

cr.Database.Tables("LossData").SetDataSource(ds.Tables(0))

Name3 = cr.Database.Tables(0).Name               'RETURNS LossData as Name3              

oldDs.Tables(0).TableName = "OldLossData"

Name4 = oldDs.Tables(0).TableName                'RETURNS OldLossData as Name4

cr.Database.Tables("OldLossData").SetDataSource(oldDs.Tables(0))

Name5 = cr.Database.Tables(1).Name              'RETURNS LossData_1 as Name 5

cr.VerifyDatabase()

The problem is that Name5 should be assigned OldLossData instead of LossData_1.  I'm not sure why it is happening and I can still run the exact same code on my XP Pro machine and Name 5 is correctly assigned OldLossData.

The report is counting on OldLossData being the alias and has tons of formulas.

Can anyone help as to why this is happening?  And how to work around it?  Thanks very much for any help you can provide.

Dan