[AccessD] Timestamp in merge database

[Anita Smith]

Thanks Borge - or is that Børge - your name sounds Danish.

Very nice explanation of the timestamp field. Unfortunately it did not cover adding a timestamp field after the replication has commenced.  I'm thinking I will add the field just before the Christmas shutdown and face the consequences.

Anita


-----Original Message-----
From: AccessD <accessd-bounces+anita=ddisolutions.com.au at databaseadvisors.com> On Behalf Of Borge Hansen
Sent: Tuesday, 14 December 2021 10:52
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Timestamp in merge database

This article may give you some tips

https://www.mssqltips.com/sqlservertip/4545/synchronizing-sql-server-data-using-rowversion/

/borge

On Tue, 14 Dec 2021 at 9:13 am, Anita Smith <anita at ddisolutions.com.au>
wrote:

> I have a database that I am converting from Access ADP to ODBC.
>
> I am coming across some issues with editing of records causing write 
> conflicts in the tables with only one user editing records. I have 
> changed all my bit fields to default and not allowing nulls as this 
> can cause this problem.
>
> I am not having much luck - however adding a timestamp field to the 
> tables fixes the problem perfectly. I am now in the dilemma that I 
> don't want to add this field to my replicated table in the fear of 
> buggering up the synchronisation (I don't want to ruin my Christmas).
>
> Is there anyone out there with any experience regarding adding 
> timestamp fields in replicated databases? I will note that the table 
> in question is only replicated one way - i.e. the subscribers don't edit the records.
>
> Anita
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com