The modProperties table stores the properties for the solution database. The properties are identified by name. Properties stored in the modProperties table must have unique names, so there are no conflicts. Properties can be set by the db_owner and can be selected by any user.
Caution You do not alter the modProperites table manually. Use the Access Workflow Designer and the Team Solutions Manager to make changes. Schema integrity is not guaranteed if you make manual changes to any solutions system tables.
The modProperties database table contains a number of columns used by the team solutions. The following table lists those columns and their data types and provides a brief description of each.
| Column | Data type | Description |
| Name | varchar(50) | Unique name for each system database property. |
| Value | varchar(256) | Property value. |
| rowguid | uniqueidentifier | Unique identifier used for replication. |
Because properties for the offline publications for a solution are stored in the modProperties table, it is important not to change these properties after the publications have been created. Changing these properties can break replication for the offline subscribers. If you make any changes to the following values stored in modProperties, you must re-create any offline publications.
Caution If you change any of these values after subscribers have taken the database offline, the offline subscriptions will be broken and any users working offline will lose offline changes. All users who have subscriptions to the publication must also re-create their subscriptions.