Hi,
I have an application written in c# UWP running on a Windows 10 tablet. It uses ultralite for the remote database. SQL Anywhere V17.0.4.2053.
Randomly, I am getting the -208 ultralite error 'Row has changed since last read -- operation canceled'...
Hi,
I have an application, written in UWP (C#), running on a Windows 10 (full version) tablet. I am using Ultralite 17 for the remote database and Mobilink for replication and Oracle for the consolidated. The tablets have a cellular connection and w...
Hi,
I'm running a .net framework version 4.6.1 application connecting to a ultralite version 17 database. The app is running on a tablet that is running Windows 10 (desktop version, not mobile). This is not a UWP or WinRT app.
I am trying to replica...
HI,
I'm running a UWP app against an ultralite version 17 database on Windows 10 Mobile Enterprise.
We've had replication fail because the column value in the ultralite database was null even though it's defined to be not null.
How could this be happ...
Hi,
I am upgrading our system to use SQL Anywhere 17 from SQL Anywhere 16. I have an Ultralite database that has 2 publications. One publication is a subset of the tables. For this publication, I defined scripts for just the subset of tables in Mo...
I'll try to get that info but since it happens randomly (enough to be a pain) I don't have a lot of control. Do you have any suggestions about what I can do when I get the error? I can check for a 208 and maybe re-run the update statement? Do you t...
Thank you for the information. I thought it was something like that. My code actually doesn't do any positioned updates. When I select from the table, I read the result set immediately and store the info elsewhere. Once I have all the data I need,...
I was mistaken. The background replication uses a different connection object. Also, the background replication only uploads records - no records in the remote are updated by the replication.
We have partial verbose logging on -vns. If the remote sent a record for update and Mobilink is set to ignore it, wouldn't that be in the log? There are some updates that we ignore on purpose and I see those as ignored in the log.
I. 2019-06-20 1...
Thanks for the though provoking questions/suggestions. The upload update script is currently ml-ignore which highlights my previous statement about not really knowing how the replication works under the hood.
At least I don't have where clause like...