How to make Mobilink server disregard error -10280

[former_member329524]

Hello, all

I have the following situation.

I have a table on the remote and consolidated side, which have slightly different structures.

The remote side has more columns than the consolidated side. The extra column is a transfer flag. When the user wishes to transfer data to the server, he updates this field then mobilink client scans the logs and send the data to the server. The table is only for upload.

I need the mobilink to transfer rows even when ony this field changes. If I do not add it to the publication, then the mobilink client does nto transfer anything.

If I add it to the publication, I get this error.

//-------------------------

E. 2015-01-28 09:28:09. Error code from MobiLink server: -10280

E. 2015-01-28 09:28:09. Server error: Message: The number of columns in client table 't507_external_clients_customer_list' does not agree with the number defined in ml_column.  Table Name: t507_external_clients_customer_list

//----------------------------

Question: If I do not need this field updated in the consolidated DB, how can I make the Moblink server to disregard it, without having to edit the consolidated DB?

[former_member188493 · Accepted solution]

What version of SQL Anywhere are you using?

What is the consolidated database?

Please show us more of the MobiLink server log.

Thanks!

[former_member329524 · Accepted solution]

All my columns are explicitely named.

Unless I specify the flag column in the publication, the mobilink client does not send the row when only this field is changed.

And if I do specify it, then the -10280 error is returned.

[former_member188493 · Accepted solution]

Also, please show us the upload scripts for that table. A solution may depend on the version and style of scripting, since different versions return different error codes.

[jeff_albion]

Hi Arcady,

If the column is defined on the remote in the publication, you will need to define the column on the consolidated using ml_add_column. To ignore the value, you can just not reference it in your synchronization scripts.

Also note that SQL Anywhere 16 has set the SQL Anywhere 12 SendColumnNames (SCN) extended option to 'ON' permanently, which removes the need to use the ml_add_column() stored procedure for version 16 remotes.

Regards,

Jeff Albion

SAP Active Global Support