I'm trying to update the record source for my report from my VB.NET application. This is the code I'm using:

Public Function SetReportConnection(ByVal oRpt As ReportDocument) As ReportDocument

Try
  Dim crTableLogonInfo As CrystalDecisions.Shared.TableLogOnInfo
  Dim crConnectionInfo As CrystalDecisions.Shared.ConnectionInfo
  Dim crTable As Table
  Dim strName As String

  crTableLogonInfo = New TableLogOnInfo()
  crConnectionInfo = New ConnectionInfo()

  crConnectionInfo.ServerName = clsSQLLogin.strServerName
  crConnectionInfo.DatabaseName = clsSQLLogin.strDB
  crConnectionInfo.UserID = clsSQLLogin.strUserName
  crConnectionInfo.Password = clsSQLLogin.strPassWord
  crTableLogonInfo.ConnectionInfo = crConnectionInfo

  For Each crTable In oRpt.Database.Tables
    crTable.ApplyLogOnInfo(crTableLogonInfo)
  Next

  Try
    strName = oRpt.Database.Tables(0).Location.ToString
    oRpt.Database.Tables(0).Location = strName
  Catch ex As Exception
    MessageBox.Show(ex.Message & ex.GetType.ToString)
  Finally
    SetReportConnection = oRpt
  End Try
Catch ex As Exception
  MessageBox.Show(ex.Message & ex.GetType.ToString)
End Try
End Function

The lines regarding getting and setting the Location were given to me by Crystal Decisions help and work MOST of the time. It is apparently required to force the report to update it's record source. However, I have a report that was working great and all of a sudden, it gets to that line and just hangs. No error message, the program just stops responding. Does anyone have any better idea on how to handle this?

Well, come to find out it wasn't hanging. The problem was that I have the report based on A SQL stored procedure. Apparently, when you set the location of a CReport, it touches the source (or Location, as they call it) and queries it for a structure. Because the stored procedure takes so long to run when you don't pass it any parameters (which apparently you can't when setting the location), it was taking about 10 minutes to even open the report window. This is before it would re-query the source based on the filters applied.

The solution: I set a "@GetData bit = 0" parameter in the stored procedure and then when I call the report, I pass it a 1. If the variable is set to 0 in the sp, I return a recordset "SELECT * FROM tblSourceTable WHERE 1 = 0". That way it would return the structure almost instantly.