An important solution feature is the ability to take a solution offline. This process is based on publications and subscriptions. Subscription information for each subscriber (for example, the team solution offline client) is stored in the modSubscriptions and modSubObjects tables.
The modSubObjects table lists all the database objects that have been replicated to the subscriber. This is used to verify whether the subscriber's database objects are out of date with the publisher's objects. The table is also used to verify whether the subscriber has modified any database objects.
Caution You should not alter the modSubObjects 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 modSubObjects 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 |
| so_ID | identity (int) | Object ID for the database object in the sysObjects table. |
| so_SubID | int | Subscription ID that includes this object in the modSubscriptions table. |
| so_Name | nvarchar(256) | Name of the database object. |
| so_Type | int | Type of the database object. |
| so_SubObjectID | int | Reserved, for internal use only. |
| so_PubObjectID | int | Reserved, for internal use only. |
| so_SubVersion | int | Version of object on subscriber's server. |
| so_PubVersion | int | Version of publication object replicated to the subscriber. |
| so_SubVersionDate | datetime | Reserved, for internal use only. |
| so_PubVersionDate | datetime | Reserved, for internal use only. |