The way our upload and download works is that we upload only
rows associated with cases that the user wants to save even though
they might have made changes to other cases as well. We then delete
from all of our case tables and then download the cases that they
download that I
notice that some of the rows that were inserts in our Remote
tables that were uploaded did not come back down. I have noticed it
specifically for a row that has been inserted that has a foreign key
to
another table row that has been inserted. The parent row gets
downloaded,
but the child did not.
On 18 Sep, 12:27, Josh Savill <no_spam_jsav...@ianywhere.com> wrote:
> Arun,
>
> The reason the row is omitted from the download stream, is because it
> already exists in the remote database. Perhaps it would be a good idea
> to explain what you're trying to accomplish so we can provide a better
> response to your question as to why you want to turn off filtering.
>
> --
> Joshua Savill
> Sybase iAnywhere - Product Manager
>
> arun.n...@gmail.com wrote:
>
> > When a row is being added
> > to the download stream, the MobiLink synchronization server locates
> > the row in the upload stream and omits the row from the download
> > stream when it is found to be the same.
>
> > a way to turn off the filter so that we download every row?
>
> > Version/build number is 10.0.1.3415
>
> > Thanks,
> > Arun
|