Do you have a PK in your table? I would add a logical field to the table. You would use table or record buffering. In the form's destroy you would save PK of marked records into some user based file (simple, but not universal solution would be to save it in a table on local drive). When the same user opens this table again from the same computer, you would restore selections for PK, which are still exist.

That's just an idea, see, if you can use it.

>I am trying to setup a grid where I can mark some records for later action.
>For example mark witch labels to print out.
>
>The first method I use was to create an array and add the record numbers of the marked records (this is the way my DOS application use to work).
>This method has the following advantages:
>
>1. quick, marking and unmarking a bunch of records goes very quick.
>2. I can save an instance on an array to disk for later use.
>3. network capable, each user can mark his own records.
>4. i don't need a field for it
>
>disadvantages
>1. maximum size of on array
>2. when I pack or re-use a recordnumber, the saved-array does not match anymore.
>
>Other people advise me to use an additional field. Here also the advantages and disadvantages.
>
>advantages:
>
>1. easy to program
>
>disadvantages:
>
>1. not network ready (everybody has the same markings).
>2. slower than the array method
>3. not easy to save to disk, when a routine was written to save the marked recordnumbers to disk the same disadvance occurs (when I pack or re-use a recordnumber, the saved-array does not match anymore).
>
>Can somebody give me his or her idea to solve this issue ?
>
>Thanks in advance...