Button click or After Update
Presume you have a field called IsFavourite?
Toggle button based on that value - could change the picture or swap the character

Wait a minute, you are saying you play favorites with people? That sounds so...

Alex I'm not experienced using toggle buttons. Are you suggesting that a toggle value (a boolean) can be represented by, say, a heart-shaped icon? Can you tell me a little more about that?

I used a command button with a picture attached for my help button.  You can make a *.png image with a transparent background, to create the star and heart shapes.  The square boundary area of the picture is transparent.  I think I used Gimp to make the background transparent.

Richard's Large Check Box video shows how to have a toggle button that changes when you click it

Jennifer Toggles can be really cool and thanks to Richard, I've added many throughout my db.  These are just from one form.

Thanks, everyone! It sounds like toggle buttons should be on my list of things to learn more about, and I'll search for tech help videos on them.

I find that trying to be too cool on a form with fancy images and buttons actually limits your application. For non-transactional tables I like to offer user-definable options and groups. (General journal entries = transactional; chart of accounts = non-transactional.) Here's a related form that does that. It's generic and it can be added to almost any form/table.

Yes, it's not a big fancy button that goes on one form, but it's a related form that can be used over and over again for lots more detail than just who is my favorite, although Option 1 could be labeled as that and handle it quite nicely.

For those that might complain that it's no fun to click in a little tiny check box, you can click on the label too and it will set the check box. That's plenty of form real estate to get the job done.

Yes, there are so many different ways of doing things in Access. (Wonder where I might have heard that...)  Databases should reflect the needs of the function and those of its users.  For some, clean and simple may be the way to go, but for others, a bit of flash and fancy may be needed to ensure the db is used to the height of its capabilities.  What I developed for work is vastly different than the one I'm developing for quilters.

Lisa is correct! If it's an "Entity" record, then there are a lot more Options and Grps (groups).