Greetings and Salutations!

>>I appreciate your efforts. I discovered a way to get around the problem but it sure is sluggish, especially if you have hundreds of items in the list. It seems that if one saves and restores the Selected state of every item in the list
that the box will behave itself. Oh, it also pays to save and restore TopItemID and ListItemID and wrap the whole thing with a ThisForm.LockScreen pair so that the whole operation looks invisible to the user -- except for a very noticeable delay.

>>Yuch. There has got to be a better way.

>PMFJI, but why don't you open the Scan'd table AGAIN and scan that other alias instead? That way you're not messing with lbox's own table, but with the same table under a different alias. That should keep your listbox intact and you'd still be able to mess with your data.

Okay, first of all I must confess that I don't know what PMFJI stands for, and I thought I knew all the acronyms! Maybe something like "put my foot..."?

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.

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. Of course, the delay involved in handling all this might not be much of an improvement of the process I described above.

Still, thanks for the thought. If I discover something wonderful I'll be sure to post it here for everyone's benefit.

Cheers, Harry