Cascading Parameter with ODBC

Hi Friends,

I have 2 parameter One is Office (Listbox) another Account(list box) , where Account list box filling is dependent on the Office selection.

In published report when I select the office from list box the page got refreshed but it not updating the account list, the account list box looks diabled?

I have define the two parameter and for the second parameter here is the query

="SELECT ACCOUNT_ID, ACCOUNT_NUMBER FROM MLGDB2.A_ACCOUNT " &
"where OFFICE_ID =" & Parameters!paramOffice.Value &
"ORDER BY ACCOUNT_ID "

To access parameter i need to use Parameters!paramOffice.Value with ODBC driver instead of @.param.

Can any one help me.

Thanks

Novin

Hi Novin,

This is something that I have done many of times. I will try and explain how to do this correctly.

1. Make a data set with your Office list

2. Make a second data set with a select statement like:

SELECT

ACCOUNT_ID,

ACCOUNT_NUMBER

FROM MLGDB2.A_ACCOUNT
WHERE OFFICE_ID in (@.Office.Value)

ORDER BY ACCOUNT_ID
3. Make sure you add a parameter to the second data set called @.Office on the parameter tab in the data set.

4. Now go to your report parameters and create two parameters. The first one is @.Office and the second one is @.Account.

5. Make sure you have the correct order Office, then Account

6. Set @.Office data set to your Office data set.

7. Set @.Account parameter to the Account dataset. Make sure to select a default value from query.

This will allow you to have a dependent parameter. Once you select the values in Office then the default will kick out the values for Account.

The way in which you explained the orginal message I am not sure will ever work

|||

Hi Thanks for your valuable reply.

I m using MS visual studio 2005, It seems like it is not supporting variablethe @.param syntext,

How to implement parameter cascading in visula studio 2005?

I found on cascading parameter implementation on MSDN for Server Business Intelligence Development Studio not for visula studio 2005.

http://msdn2.microsoft.com/en-us/library/aa337426.aspx

Thanks

Novin.

|||

Hi

The implementation is working it was a silly mistake from my side i have assign wrong data type the the paremeter.

Thanks,

Novin