>Anyway, I'm using the Selected property of the items in the list to do something to the view. The only way I know to reliably be sure of which record in the view corresponds to each item in the list is to SCAN ENDSCAN side-by-side with the FOR i=1 TO This.ListCount statement. The original table has many more records than the view and doesn't have the one-to-one relationship.

You can Use TheSameView Again In 0 Alias DoubleVision, or whatever the names you may pick, and manipulate that. Now in using the same view twice, there's a strong difference in parametrised views - if you use it AGAIN you get the same data; if you just use it with a different alias, you may get a different set of data if the parameters have changed.

>A possibility does strike me though: if I went through the pain of creating two identical views, one to display and one to manipulate, it might work just as you describe.

As you see, no need for creating it - just use the same one again. Just try it.