I'm curious: to know how you all generally deal with the "3-way" logic problem RE attributes. What I mean by this is, let's say you want to have an attribute called "Gifted", that denotes whether a student is on the gifted track or not. You can create a yes/no attribute, but then you get three possibilities: Yes, No, and blank. [i.e, not specified on the student record]. Do you make it required and have it automatically applied to all new records? Will it go into old records? I suppose I could just create a yes/no field, leave it optional, and specify 'Yes' when I mean for a student to have it, but I just *know* that someone somewhere is going to add the attribute to the user and leave it at the value "no"....

If you make an attribute required, it will then require that all new records have that attribute or they cannot be saved. If you are making changes onto an existing record, you may have to add the attribute in order to save your attribute but otherwise, there is no impact to older, existing records. Most clients I have worked who use a similar attribute have built it as "Track" and then set it up as a table with a value for Remedial, Regular, Gifted and made it required so that it could not be left blank. I hope that you find that helpful.

Thanks for the input. I like the idea of requiring the attribute, tho it could get to be a nuisance to have to provide it w/every change to pre-existing records. Hmm....guess I could load default values en masse. -j

Yes, the information can be globally added to all students (or just all Current Students) by using Global Change, Students, New Global Change and within the Attributes subsection, there is the field Attribute. When you select that field you are able to Globally add the attribute Category, Description, Date and Comments from one window. It might be easiest to mark everyone No and then just change those students who are exceptions. Have a great weekend!