Logon Error for Crystal Report Viewed by User When Not Included In App

Question

I have a Visual Basic 2008 SP1 application and I'm using Crystal Reports 2008 SP0 (with FP1 + 2).  I have about 50 reports using integrated security that are all "embeded resources" in the application.  When I want to print one of these reports I use code like this:
PrintReports(New MyEmbededReport)
And in my PrintReports routine it just creates a new instance of a form that has the report viewer control on it and passes the report over to it.  This works GREAT and I can embed all my reports right into the app and call them when I need them.
Recently however I've had the need to add some custom reports that may change more often then the app changes so I need a way for users to access their reports without a new version of the app being pushed out.  So I made a routine that lets me store the actual Report.rpt file into SQL and when a user goes to run it the report is pulled out of the database and saved into their temporary files and then passes it back to my PrintReports routine as a ReportDocument.  This also works fine but only on my machine.  On the client machines it asks for the login information and no combination will work.  I've tried multiple ways of getting around it and have spent hours trying examples found on the internet including assigning the login information before preview, running through and assigning the login information to each table, I've gone through the "Using Integrated and SQL Autentication in .Net Applications" guide, turning on and off integrated security.  Nothing seems to work.
What else is there to try?  As a very last resort I will have to store the reports into the app like the other ones but I'm really trying not to do this.
-Allan

Answer 1

Just trying to get this working.  My PrintReport routine used to just have the single line to assign the passed report to the report viewer.report source property.  I've changed it to this:
            Dim crtableLogoninfos As New TableLogOnInfos()
            Dim crtableLogoninfo As New TableLogOnInfo()
            Dim crConnectionInfo As New ConnectionInfo()
            Dim CrDatabase As Database
            Dim CrTables As Tables
            Dim CrTable As Table
            'Set the ConnectionInfo properties for logging on tothe Database
            With crConnectionInfo
                .ServerName = My.Settings.SQLServerName
                .DatabaseName = My.Settings.MainDatabaseName
                .IntegratedSecurity = True
            End With
            'This code works for both user tables and stored procedures.
            'Set the CrTables to the Tables collection of the report
            CrDatabase = myReportFileName.Database
            CrTables = CrDatabase.Tables
            'Loop through each table in the report and apply the LogonInfo information
            For Each CrTable In CrTables
                crtableLogoninfo = CrTable.LogOnInfo
                crtableLogoninfo.ConnectionInfo = crConnectionInfo
                CrTable.ApplyLogOnInfo(crtableLogoninfo)
            Next
            'Set the viewer to the report object to be previewed.
            PrintPreview.CrystalReportViewer.ReportSource = myReportFileName
And I have the exact same issue....my internal reports stored within the app still work fine for everyone but the custom reports made in CR2008 and added as files still do not. 
So out of fustration I added one of the "external" reports into VB 2008 and opened it in there, did a verify database, saved it, and then added it to my SQL server but again same issue....it's like when its off of my computer it "loses" the connection information even though it still shows its there.  Not sure why the reports that are embedded into the app don't have this issue. 
So that gave me another idea.  I took one of the reports that was originally created in VB2008 and took that and put it into the SQL then ran that like the others and IT WORKS.  It creates the temp file on the client PC and runs it from there with no login issues.  Now I'm more confused....any ideas?  I guess I'm going to start recreating the reports I created in CR 2008 and remake them in VS 2008 since those seem to work fine but why should I have to....what would be the difference?
-Allan