The modPublications Table

See Also

An important Access Workflow Designer feature is the ability to take a team solution offline. This process is based on publications and subscriptions. Publications are defined by the solution developer and are stored in the modPublications table and the modPubObjects table. This information is used to create SQL publications. A user then creates a subscription to that publication to create the offline version of the solution.

The modPublications table stores all the attributes required to define an offline publication. The table is used to create and re-create publications and to enforce run-time permissions.

The publication list exists before any publication is created in the database. Therefore, the ID is an identity column generated by this table and not the publication ID generated by SQL when it creates the publication.

The link between the publication list and the SQL publication instances returned by the stored procedure sp_helpmergepublications is maintained by using the publication name.

Caution   You should not alter the modPublications 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 modPublications 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
pub_ID identity (int) ID of the publication used only by the modPublications table.
pub_Name nvarchar(256) Name of the publication.
pub_Description ntext(16) Description of the publication.
pub_Permissions ntext(16) Type of permissions to be enforced: A = any, M = many, N = none.
pub_DefaultFor ntext(16) Reserved, for internal use only.
pub_Schedule nvarchar(1024) Default schedule information for synchronizing the user.
pub_State int Reserved, for internal use only.
pub_POV numeric Reserved, for internal use only.