The modApplications table is a directory table for team solutions stored in the modSystem database. It holds a list of all the properties associated with each solution registered on the server. This information is used by Team Solutions Manager and by the workflow time-out job when executing time-based events.
Caution You should not manually alter the modApplications table. 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 Access Workflow Designer system tables.
The modApplications 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 |
Id | identity (int) | Unique identifier for each solution. |
Caption | nvarchar(256) | Friendly name of the solution used by the administration components (for example, "Issue Tracking Solution"). |
Description | ntext | Textual explanation of what the solution is. |
Server | nvarchar(128) | Name of the server where the solution database is deployed. |
Database | nvarchar(128) | Name of the solution database (for example, "TeamIssues"). |
WebServer | nvarchar(512) | URL for the Web server that contains the solution folder. |
Folder | nvarchar(512) | Name of the Microsoft FrontPageŽ Web folder on the Web server that contains the Web files. |
Start_page | nvarchar(512) | URL for the start page for the solution. |
Summary_page | nvarchar(512) | URL for the summary page for the Web solution. |
Owner | nvarchar(128) | Name of the user who created the Web solution. |
Available | bit | If 0, the Access Workflow Designer can register the solution but cannot make it available on the server. |
Properties | ntext | Reserved for user-defined properties. |
OfflineDatabase | nvarchar(128) | Name of the solution offline (for example, if the online database is called "TeamIssues," the offline database might be called "TeamIssuesOffline"). |