I know this isn't .net, but you guys here seem very knowledgeable and I am DESPIRATE for an answer. 

I'm 99.9% sure I've got the code right.  Just that some reports work and other do not, with the same code.  All reports use stored procedures as ther source/tables.  The only difference we can see is that reports that do not work have a date parameter and the ones that do work do not have a date parameter.  For the reports that do not work, no parameters are getting set.

Code sample (is very abbreviated, but wanted to show the basic of the code):
    For i = 1 To g_CrystalReport.ParameterFields.Count
        Set CRParameter = g_CrystalReport.ParameterFields(i)
        With CRParameter        
            Select Case .Name
                Case "{?@Portfolio}"
                    Call .SetCurrentValue(strPortfolio, crStringField)
            End Select
        End With
    Next i

I tried the new functionality using method AddCurrentValue, but that works worse, if that makes sense!  I don't want to get too long in this email.

I'm pushed for time and need this done tonight!

Thanks to anyone who can help!!

Brian,

I'll try anything at this point!

The parameters are Crystal parameters and then passed to the stored procedure.

I've already traced and Crystal is sending the old (stored from development of the report) to the server.  In fact, I have steped through the code...checking the parameters current before setting (old value) and then after setting the current value (still old value). 

The dates are all datetime in Crystal.  I am passing a VB date field. 

It's 'funny' because the date is the last parameter in the list, but no field is getting set.  I am going to try making the date a string...  I'll post again when I'm done.