This is related to a problem that I described and posted in the "Finding and Sorting" forum.

In my database, I have one layout that is a common menu (i.e. button bar) and another layout that shows the list of music (vocal solos for singing in church) in the database. In the list view, if I limit the found set to 1 of 1 (from 1 of 2), and switch to the menu layout, the found set changes to 1 of 2. I verified this by using the data viewer to track the value of the "_found" field in the music table. So, it appears that switching to a different layout that is associated with another table will change the found set. On a hunch, I changed the menu layout so that instead of being associated with the menu table, it is now associated with the music table, and the problem seems to have been solved.

So here's my question: Is there any harm, and/or am I going to run into any problems, with showing records from a table that's not really associated with the things on that layout?

Jonathan

musicdatabase.fp7.zip

Each Table Occurrance can have its own found set. This makes sense, since each table contains a different set of records.