InfoPath Dev

I have applied the cascading list box approach with a database connection in a form I have built.  I have created a simple Access database to test.

When I make a selection in the first list box, the second list box provides filtered data accordingly.  However, it only seems to show the first 15 values of the filtered data.  Is there a limitation as to how many rows can be shown in a list box?

The other problem I'm having is that I've entered additional data into the database, but it is not been reflected in the list boxes within the form.  I set the Database data connection wizard checkbox 'Store a copy of the data within the form template' to yes intitally and then have subsequently removed it.  I am wondering if there is some level of the form using a stored version and not pick up the updated values?

Your help is appreciated,

Simon

To answer your first question, no there's no limit to the number of options that can be shown in the drop-down list box control. However, an excessive number of options will have performance issues.

Try removing the filter to discover whether it is a problem with receiving data from the db connection or whether it is a fault of the filter itself.

I believe I've found the problem which may be useful for others to know.

On further investigation, the latter list boxes were limited by the number of rows in the first list box.  The reason for this is, the InfoPath data connection wizard defaulted the relationships between the tables to the primary key field for each.  Thus if there were 15 rows in the first table, you would only get the first 15 rows in the second and so on.  I had to change the relationship to the primary key of the first table to it's equivalent lookup field in the second and so on.

Thanks for sharing this. I know it will be very useful to people in similar situations! I'm glad you got it working.