In the following table, the description provides the SQL data type. If you are writing your script in Java or .NET, you should use the appropriate corresponding data type. See SQL-Java data types and SQL-.NET data types.

In SQL scripts, you can specify event parameters by name or with a question mark. Using question marks has been deprecated and it is recommended that you use named parameters. You cannot mix names and question marks within a script. If you use question marks, the parameters must be in the order shown below and are optional only if no subsequent parameters are specified (for example, you must use parameter 1 if you want to use parameter 2). If you use named parameters, you can specify any subset of the parameters in any order.

This event lets you record the time when the download was successfully applied at the remote database.

This event is only called when using download acknowledgement. The download transaction is committed and the synchronization ends when the download is sent. This event is called when the synchronization client acknowledges a successful download. This event is called on a new connection, after the end_synchronization script of the original synchronization. The actions of this event are committed along with an update to the download time in the MobiLink system tables.

Due to the special nature of this script, any connection-level variables set during the synchronization are not available when this event is executed.

• publication_nonblocking_download_ack connection event
• dbmlsync: SendDownloadAck (sa) extended option
• UltraLite: Send Download Acknowledgement synchronization parameter

The following script adds a record to the table download_pubs_acked. The record contains the remote ID, the first authentication parameter, and the download timestamp.

INSERT INTO download_pubs_acked( rem_id, auth_parm, last_download )
   VALUES( {ml s.remote_id},  {ml a.1}, {ml s.last_download} )

The following call to a MobiLink system procedure registers a Java method called confirmDownload as the script for the nonblocking_download_ack event when synchronizing the script version ver1.

CALL ml_add_java_connection_script(
   'ver1',
   'nonblocking_download_ack',
   'ExamplePackage.ExampleClass.confirmDownload' )

The following is the sample Java method confirmDownload. It calls a Java method to perform business logic based on the download being confirmed, up to the given timestamp, for the given user.

public String confirmDownload( 
  String user,
  Timestamp ts ) {
  actOnConfirmedDownloadTSForUser( _syncConn, user, ts );
  return( null ); 
}

The following call to a MobiLink system procedure registers a .NET method called ConfirmDownload as the script for the nonblocking_download_ack connection event when synchronizing the script version ver1.

CALL ml_add_dnet_connection_script( 
 'ver1',
 'nonblocking_downlolad_ack',
 'TestScripts.Test.ConfirmDownload'
)

The following is the sample .NET method ConfirmDownload. It calls a .NET method to perform business logic based on the download being confirmed, up to the given timestamp, for the given user.

public string ConfirmDownload(
  string user,
  DateTime ts ) {
  ActOnConfirmedDownloadTSForUser ( _syncConn, user, ts );
  return ( null );
}