Reconnect Process for New Occurrences

No Database Connection

Uniface does the following for all disconnected occurrences with modification status new and no connection to the database:

1. Uniface searches for the occurrence in the component using the disconnected occurrence Id.
2. If the occurrence exists in the component, the reconnect process continues at step 4.
3. If the occurrence does not exist in the component, Uniface recreates the occurrence using the same disconnected occurrence Id.
4. Field data is copied from the disconnected occurrence.
5. Occurrence modification flags are set to New ($occmod=1, $storetype=1).
6. Field modification flags are set to Modified ($fieldmod=1).
7. The disconnected occurrence is deleted, and the reconnect process continues with the next disconnected occurrence.

With Database Connection

Uniface does the following for all disconnected occurrences with modification status new and a connection to the database:

1. Uniface searches for the occurrence in the component using the disconnected occurrence Id.
2. If the occurrence exists in the component, the reconnect process continues at step 4.
3. If the occurrence does not exist in the component, Uniface recreates the occurrence using the same disconnected occurrence Id. Uniface does not search for the occurrence in the database.
4. Field data is copied from the disconnected occurrence.
5. Occurrence modification flags are set to New ($occmod=1, $storetype=1).
6. Field modification flags are set to Modified ($fieldmod=1).
7. The disconnected occurrence is deleted, and the reconnect process continues with the next disconnected occurrence.

Note:  After the reconnect process, key validation should be used to check for duplicate keys in the database.