Showing posts with label parameter. Show all posts
Showing posts with label parameter. Show all posts

Tuesday, March 20, 2012

Processing report

Hello,
In my MS report I have 4 textbox parameter and One dropdown parameter
two of the textboxes and the dropdown has queried parameter. All of them
have default parameter.
The issue I am facing is that When ever I click on the preview Report on the
dev machine, My report starts to do "Processing Report" with the "View
Rreport" button disabled. The processing report keeps on going although the
query runs fine in QA in 2-3 minutes.
I want the preview report should start processing only when I click "View
Report" so that I can drill down to real problem.
I have tried removing one of the default parameter so that it waits for
parameter but it does not helps..
Any suggestions will be highly appreciated...
Cheers,
siajYou said: "All of them have default parameter."
If all parameters have a valid default value, the report will run
immediately. This behavior cannot be changed in report manager. You could
remove the default value e.g. from the last report parameter which will
prevent running the report immediately.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"siaj" <siaj@.discussions.microsoft.com> wrote in message
news:4AB4CCCF-4485-4380-9918-57F6DFF80B10@.microsoft.com...
> Hello,
> In my MS report I have 4 textbox parameter and One dropdown parameter
> two of the textboxes and the dropdown has queried parameter. All of them
> have default parameter.
> The issue I am facing is that When ever I click on the preview Report on
> the
> dev machine, My report starts to do "Processing Report" with the "View
> Rreport" button disabled. The processing report keeps on going although
> the
> query runs fine in QA in 2-3 minutes.
> I want the preview report should start processing only when I click "View
> Report" so that I can drill down to real problem.
> I have tried removing one of the default parameter so that it waits for
> parameter but it does not helps..
> Any suggestions will be highly appreciated...
> Cheers,
> siaj
>

Processing of Table in a report, delayed based on input parameter

I have input parameters which are dates in my report. My problem is I
have to validate these parameters before I display the table in the
report. Currently I am handling this by using the "Visibility"
property of the table. But I wanted to know is there is any other way,
I can stop the processing of the table till I validate the input date.
Thank You.Your query parameter can be an expression instead of directly mapped to the
dates. Then use code behind reports to validate the dates. Set the date to a
know bogus date that returns no data.
To map to an expression go to data tab, click on the ..., parameters tab.
Pick expression instead of the report parameter.
Another vaiation of the above. Have hidden parameters. Set the value of the
parameter to an expression that references the visible date parameter (and
again use code behind report). Then map this hidden parameter to your query
parameter. This hidden parameter can also be used for visibility. Hide the
data (by setting to a date that returns no data then it would be empty
anyway). Then show a textbox with your comment on why the date is invalid.
The above should at least point you in the right direction. Some of this
will be a hack but you should be able to get something acceptable worked
out.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
For instance
"ricky" <G.RekhaDevi@.gmail.com> wrote in message
news:55dde3ac-e215-44c3-8a9b-e3f20987e0b8@.i72g2000hsd.googlegroups.com...
>I have input parameters which are dates in my report. My problem is I
> have to validate these parameters before I display the table in the
> report. Currently I am handling this by using the "Visibility"
> property of the table. But I wanted to know is there is any other way,
> I can stop the processing of the table till I validate the input date.
> Thank You.

Monday, February 20, 2012

Procedure x expects parameter @y which was not supplied.

I'm trying to update a member's record via stored procedure. The procedure is thus:

*********************************
CREATE PROCEDURE upd_MemberProfile(
@.MemberID VarChar(10),
@.FirstName VarChar(20),
@.LastName VarChar(20),
@.Address VarChar(50),
@.City VarChar(40),
@.StateID Char(2),
@.ZipCode Char(5),
@.Email VarChar(30),
@.PayPalSubscrID VarChar(22)
) AS

UPDATE Members
SET FirstName = @.FirstName, LastName = @.LastName, Address = @.Address, City = @.City, StateID = @.StateID, ZipCode = @.ZipCode, Email = @.Email, PayPalSubscrID = @.PayPalSubscrID
WHERE MemberID = @.MemberID
GO
*****************************

The call from the Webpage is like so:

*****************************
...
Dim Subscr_id As String = "123ABC-HDTV"

Try
cmd.CommandText = dbo() & "upd_MemberProfile"
cmd.CommandType = CommandType.StoredProcedure

With cmd.Parameters
.Add("@.MemberID", MemberID)
.Add("@.FirstName", FirstName)
.Add("@.LastName", LastName)
.Add("@.Address", Address)
.Add("@.City", City)
.Add("@.StateID", StateID)
.Add("@.ZipCode", ZipCode)
.Add("@.Email", Payer_email)
.Add("@.PayPalSubscrID", Subscr_id)
End With

If cnn.State.Open Then
cnn.Close()
End If

cnn.Open()
cmd.ExecuteNonQuery()
cnn.Close()

Catch ex As Exception

'Notify Admin of the Problem
MailUsTheOrder("ERROR on upd_MemberProfile: " & ex.Message)

'Close the SQL Connection
If cnn.State.Open Then
cnn.Close()
End If
End Try
******************************

This was working two weeks ago. I have changed NOTHING and now I get the error:

Procedure 'upd_MemberProfile' expects parameter '@.PayPalSubscrID', which was not supplied.

Any Ideas?yup. you might not be setting that parameter in another method or something. Do you have any overloads or anything? step through the application, and see if the right method is being called.|||Hi,
is your Subscr_id 's value nothing?