Using the same forms data for multiple sites

Consider this information:

• By default, all SyteLine databases are defined as "all-in-one" databases that have at least one site, one set of forms data, and one set of objects data.
• In most cases, we recommend that you use the standard, all-in-one database, and just use group-level customizations and permissions if you want to assign particular forms data to certain users. However, you can optionally set up a separate all-in-one database that you use only for personalized forms or objects data.
• For example, you might want to display different forms for the same users when they sign into site A vs. when they sign into site B. In that case, you could set up configurations for site A and site B that point to different databases for forms data.
• You also might want to use different databases to hold forms for different communities of users. For example, sites in some areas may need to see a set of custom forms or custom fields, and users at other sites would not require them. However, by pointing to one database that holds the forms customizations for a group of sites, you can target customizations by group.
• If you have multiple sites in multiple databases, and they will be looking at the same version of the SyteLine application and the Mongoose framework, it might make sense to point them all to a single database that contains form customizations that all the users at those sites would see.
• Since forms "traffic" is mostly read-only access, having many users/sites pointing to a database for forms usually does not present performance problems.
• By default, the database that stores forms data for a site configuration is the same as the application database for the site. If you want a site to point to a different database for forms, use the Configuration Manager utility to create a configuration for the site. In the Runtime (Client) tab, specify the other database as the Runtime Forms Database.