I'm using a master Appointments database table to store all appointments for RadScheduler that we use. That way I can share the same table whether it's a Dr. Appointment or a Vacation Schedule etc. I've added an "AppointmentType" column to the table to differentiate between appointment types. What I don't understand in this scenario is how to handle Resources. I don't want to store the ResourceType.ForeignKeyField in the master Appointments table because each type of Appointment may have zero to multiple Resources. I'd rather off-load Resources to another table so I don't clutter up the master Appointments table with FK Resource ID's for every possible Resource. Any ideas?