MobiLink Synchronization Reference
Stored Procedures
Client event-hook procedures
Use this stored procedure to add custom actions when communications errors occur while reading the download stream sent by the MobiLink synchronization server.
| Name | Values | Description |
|---|---|---|
| table name (in) | table name | The table to which operations were being applied when the error occurred. The value is an empty string if dbmlsync is unable to identify the table. |
| publication_n (in) | publication name | The publications being synchronized, where n is an integer. There is one publication_n entry for each publication being uploaded. |
| MobiLink user (in) | MobiLink user name | The MobiLink user for which you are synchronizing. |
| script version (in) | script version name | The MobiLink script version to be used for the synchronization. |
If a procedure of this name exists, it is invoked when a communication error is detected during the download phase of synchronization. The download is then terminated.
This procedure executes on a separate connection, so that failures can be logged. Otherwise, the action of logging would be rolled back along with the synchronization actions. If dbmlsync cannot establish a separate connection, the procedure is not called.
By default on Windows CE devices, synchronization tables are locked in exclusive mode, which means that this hook cannot successfully execute if it requires access to any of the synchronization tables. It also cannot execute if it needs to access synchronization tables and you set the dbmlsync extended option LockTables to EXCLUSIVE. For more information, see LockTables (lt) extended option.
Actions of this procedure are committed immediately after execution.
Synchronization event hook sequence