July 12, 2008 at 5:32 am
plz suggest me reason & solution of above error
July 12, 2008 at 6:34 am
Could you post the full error message and perhaps some description of where and how you get it?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 12, 2008 at 10:57 am
Without further information, this is just a WAG on my part. I would guess that you have setup parameters in your report and one or more of your parameters references a parameter that is setup later.
For example, if parameter1 has as it's source:
SELECT somevalue FROM sometable WHERE column = @parameter2;
This is not allowed, since parameter 2 has not been defined yet. To fix this, you have to move parameter2 up so it will be created before parameter1 needs it.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 15, 2008 at 1:04 am
Hi,
I think Jeffrey Williams is right.
Your parameters have casecade dependecy. So you need to set the proper order of parameter.
e.g there are 3 parameters: Country, State, and City.
And State is dependent on Country and City is dependent on State.
So the order of Parameter should be maintained in parameter window.
July 15, 2008 at 4:10 am
thnk u williams
its working
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply