Checking In Objects

Checking in a form or global object replaces the original version in the master database with the edited version from the run-time database. This action effectively makes the changed object the official current version.

You can check in an object only if one of these situations is true:

• You have the object checked out.
• The object is new and does not exist in the master database.

You can check in these objects:

• Forms, with or without their associated templates and/or global objects.
  Note:  To check in associated templates and/or global objects, you must have those objects checked out as well.
• Global objects, regardless of whether they are associated with forms.

During a check-in operation, Form Control performs these tasks:

• Verifies that any objects you are trying to check in were checked out to you, or that the objects are new and do not exist in the master databases.
• Copies the objects from the run-time databases to the appropriate master databases.
• If your system is integrated with a source control system, checks the objects into source control.

  Following check-in, Form Control displays a dialog box that indicates any generated files that were not checked in or added to source control.

• Unlocks the objects in both the master and run-time environments.

  That is, the LockBy column contained in the form and templates databases is set to an empty string, indicating that no one has the item checked out.