Storing found sets

[sandyinlet]

My client requires at least a dozen "slots" where they can store the current found set of contacts, give that set a name, and then later recall that set at will. I'm looking for an efficient way to do this. Here's my thought experiment thus far.

Create a dozen "standalone" contact table TOs, nothing linked in or out, create empty layouts based on each of those TOs, then script routines to store and restore to and from these specialized layouts. (I've done this for a singleton TO and it works.) Then give the user an interface where they can choose and name each of these slots and the action of storing or of restoring.

What's giving me pause is my feeling there is probably a more efficient way to achieve the same result. I'm especially concerned the client will then want 50 or 500 slots. The above system may not be all the most efficient way to give the client what he wants.

Your thoughts appreciated.

[mr_vodka]

Why not have a table that stores what table they want the stored set for ( depending on layout ), who they are, and the Unique IDs into a multi-line field. You can quickly recall a found set by setting a global field with the IDs and then using a GTRR.