Select Tools»Source Code Control»Launch SCC Provider to display the Source Code Control window. In the Source Code Control window, select Tools»Administrative Configuration to display the Administer Builtin System dialog box.
Note This dialog box is available only in the LabVIEW Professional Development System.
This dialog box includes the following components:
Master directoryThis is the location where the source code control tools store the files you add to SCC. It is important that all users have access to this directory. If you want users to be able to modify files, they need to have read/write access to this directory. The built-in SCC system copies files to this directory as they are checked in and out and maintains history information for each file within this directory. Consequently, you should make sure that this directory has adequate disk space. Windows Each user should connect to the volume that contains this directory and map that volume as a network drive, for example, as D:\ rather than as a UNC path of the form \\machine\ volume. Because UNC filename support varies slightly among Windows operating systems, the SCC tools do not support UNC filenames.
Backups of previous versionsIf you decide to maintain file backups, the SCC tools make a copy of the old file when a user checks in a file. You can configure the system so no backups are maintained, a specific number is maintained, or there is no limit on backups. If you choose to have no limits on backups, you need to delete old versions periodically to avoid running out of storage space on the server.
Using File PermissionsMarks files as read only when you check them into the system and read/write when you check them out of the system. This works well for most developers and many work environments.
Using Internal LockingWith this option selected, the built-in SCC system locks checked-in files. If you open the Security Properties page, you see that the VI is locked. When you check files out, the built-in SCC system unlocks them. Internal locking is recommended for multiple platform development such as Windows, Macintosh, and/or UNIX development, because the SCC tools can distinguish between user edits and a recompile that occurs when you load a VI that was built on a different platform.