InfoPath Dev

I have read all of the articles on creating a unique list in a dropdown that is using values from a secondary data source this forum.

I have a form with cascading dropdowns. These are working great! However I have repeating values in the first box.

I am retrieving data from a SQL database to populate the dropdown. The name of the secondary data table is SW-VERSIONS. The name of the field is MACHINE.

Here is the syntax that I enter when creating a filter with an expression as outlined in Greg Collins article Create a Cascading List form a Flat Data Source.

not(.=../preceding-sibling::SW-VERSIONS/@MACHINE)

I have also used
not(.=../preceding::SW-VERSIONS/@MACHINE)

Neither one of these work. Any help is appreciated.

If the data is in a SQL DB, if you are using a select statement, why not do a select distinct?

Hi Oakridge and welcome,
Very well articulated e-mail post. Not sure why the preceding-sibling isn't working. Some issue with secondary DOM perhaps? You might try with main just for fun. Greg might know. I'll forward to him.

Patrick Halstead [InfoPath MVP]
InfoPathDev

It could be the structure of your schema. 1) What does your schema look like. 2) What node are you binding the drop-down list to? 3) In what order are the filters placed for this control?

Greg Collins [InfoPath MVP]
InfoPath Dev

whats the correct syntax for doing this in a access db table