checkbox values are not stored in a database. the database stores e.g. boolean values or what ever you map to a checkbox (like "ja" for checked or "nein" for unchecked and "indifferent" for intermediate state). so, this question is hard to answer and depending on your, let's call it implementation strategy (database first, code first, model first). however sticking to conventions and using the entity framework for your database mappings, esp. when using the "code first" approach, may leave the persistence concerns, and there for the loading, to the magic of the framework (you can have a largely transparent persistence layer). another approach is mapping your db-module/ schema to your domain objects (pocos) either by hand or entity framework (or any other orm/ odm framework) using either annotations, or a fluent api or some other programming manner I forgot to mention. dive deeper into the matter of persistent frameworks (I sugest using the entity framework) and find out. see for example
Entity Framework Code First: Mapping to Existing Table in the Database[
^]
in simple words: map a Boolean property of your selectable objects to a column in your database and let the entity framework do the binding for you and set the checkbox state programmatically in your code.