If both Push succeed, there will be no error. In a scenario with 2 users
Pushing data, and you expect the data to be over written, then you are
really looking for some type of Conflict resolution. There is no Conflict
resolution for Push. You will need to provide that logic ahead of time in
order to maintain your data. Using Identities and Unique ID's helps keep
data integrity and and correct.
If you do not want to provide the logic for Pull, please take a look at
Replication. With a little more overhead, Replication provides some logic to
help maintain your data.
Brad
This posting is provided "AS IS" with no warranties, and confers no rights.
> A follow up question (It seems like I don't fully
> understand PUSH errors !) :
> - A user PULL a record.
> - Another user PULL the same record.
> - Both users do updates on different recordfields.
> - Then both users do a PUSH.
> - Will this create PUSH errors ?
> Regards,
> Lennart N.
> >-----Original Message-----
> >From the SQL CE Books On Line:
> >RDA tracked Pull and Push methods use optimistic
> concurrency control. SQL
> >Server does not keep pulled records locked. When the
> application calls Push,
> >the changes made to the local SQL Server CE database are
> unconditionally
> >applied to the SQL Server database. This may cause
> changes made by other
> >users of the SQL Server database to be lost.
> >Brad
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >> Hi !
> >> Scenario :
> >> - PULL 2 records from the SQL Server 2000 with
> TRACKING
> >> ON and error table specified.
> >> - Using the QA I make a change to one of the records
> >> at the SQL Server 2000.
> >> - Make changes to the records at the Pocket PC
> emulator.
> >> - Do a PUSH from the Pocket PC receive status OK
> >> no error message ?!
> >> - Changes made at the Pocket PC emulator overrides
> >> the one earlier done at the SQL Server 2000 !
> >> Any idea ?
> >> Thanks
> >> Lennart N.
> >.