I have not yet experienced a situation like that but would be interested in viewing such a video.  Great suggestion.

That does sound like a good idea for a video. I would suggest using either two subforms where you move items from one to the other, or two list boxes where you can move items from one to the other and then just save those results. I think the easier one would be subforms or even just two open forms. Either one would be great. I'll add this to the list. This would be a cool video. And this would work for anything - like you said, band set lists or things with components. Let's say you want to build a computer system, you just pick items from the list on the left and add it to the list on the right. I mean, there you'd have to do one item from each category - like one hard drive, one memory, one processor. But I guess that would pretty much be the same thing with a band too. You wouldn't want to repeat the same songs... well, sometimes you did, I used to be in a band back in the 90s. Sometimes we'd have a really popular song we played early in the evening and then play it again at the end of the night because you sometimes get two different crowds by that time.

Peter sorry, I accidentally deleted your reply:

Thanks Richard; I'd love to see you take a crack at this topic. In the meantime, I'm trying to visualize how it would work, starting with the Tables. --you'd have a Table for Songs, clearly. with fields for SongName, date released, key, tempo, keyboard settings, etc., perhaps pulling composers, recording artists, etc. from separate tables. --Then, I'd expect you'd have Table for Gigs -- date, location, hours, comments, etc. -BUT Then I'm stumped at the point of Sets. ----do you have a separate Table for each Set? ----Is each Set from each Gig a separate record within the Table?, e.g Set 1 from Gig 1 is a different record from Set 1 from Gig 2, etc. ----And how do you deal with the fact that each Set could have 10-15 different songs. Your comment above suggests that you'd somehow use Forms and List Boxes in lieu of a Table for the Sets themselves? Thanks for your interest in this topic.

No, you never use forms in lieu of a table because all of the data gets stored in tables. It's just you display them in forms. You would obviously have a table for your songs. You could make a table for the gig and then make a set list table that would be related to gigs. Into that table, you would copy songs. You'd set up a custom sort order so you can move them up and down. You can either have multiple sets per gig or you could just do it as one set list and put breaks in there wherever you want it. Make a song called Break. That'd be easier. But multiple sets obviously would work too. Well, everything so far goes into tables. That's the only place data is stored. Then you just have to decide how you want to work with that using your forms. You could either use multiple open forms, you could use a form with two sub-forms with continuous forms inside them, you could use list boxes. There's a lot of different ways to do it. I'll try to keep it simple at first and maybe do a little more expanded, extended cut. But I do cover all of this stuff in my full course, obviously not with set lists, but I cover moving items between multiple boxes in several of my videos. But to do it automatically will either involve manually copying and pasting or a little VBA code to put inside of a button. For example, Access Developer 15.

Thanks Richard. I'm trying to visualize what a set list Table would look like. Does this sound right?: It would have 30-50 slots [fields] for songs pulled from the song table. it would have a field for Gigs, pulling the Gig ID in as a Foreign Key. Then a field for SetNo. {e.g. 1-3 or 1-4) and then a field for Order within sets (1-12 or 15 or whatever). then I could Sort first by SetNo. and then by Order. and yes each Set No. would include a song called Break (or whatever), with an Order of Zero so it would sort first for each respective Set. The unique SetList Record would be the combination of Gig/Song/SetNo./Order.  It just seems like table would have lots of redundancy, i.e.  mostly the same 30-50 songs repeated for each gig, the records differing only in the Field combinations of SetNo/Order/GigID
Well, if you're planning to do a video, maybe I should stop bugging you with questions and just wait and see what you suggest there.
thanks a lot for your interest in this!

Yeah, I think you should probably just wait for the video because I could spend more time explaining it to you here than I could just recording the video lol. Right now, the series that I'm working on for TechHelp is about fitness, diet, and exercise, and something similar will be in this where you can pick food items and create meal plans based on that. So you pick a food item, you put it in your meal plan, and it's going to be kind of the same technique. So maybe watch that too before I get to this one for you.

Will do, I'll be sure to check out the fitness/diet etc. video. thanks again for fielding these inquiries.