search for: integer20

...ificance of each field. What isn''t clear to me is the toll this would take on a database. Say my CONTACT looks like: CONTACT: first_name, :string last_name, :string string1, :string string2, :string ... string20, :string integer1, :integer integer2, :integer ... integer20, :integer If there are hundreds of users each with hundreds of CONTACTs, these extra fields lying around will take up space. Granted, unused ones will be NULL, but still taking up space. Another option is to place the "user-specified" fields in a separate table, but this seems less...