I also found the same info about the null bit fields, but just a couple of
days ago I figured out what it seems like the real problem was. In the
tables I was having problems with I had some default values specified. When
I created a new record and only updated certain fields, then when that was
inserted into the server table the default values were added. Then my guess
is that the resync command re-looked up the table and found those fields
with the default values different from what they were before. Maybe this
> I get the same message in the same situation... I found a solution for a
> part of the problem. If you had yes/no field type in Access before
> your back-end, SQL replaced the 0 for "null" values. This makes SQL think
> that there has been changes since the last update. All you have to do is
> replace all the "null" for 0 in the bit fields.
> Hope this help!
> I still have the problem but not for the same reasons, there must be
> similar cause...I'm working on it since last week, if anyone has answers,
> please send it to me, i've tried a lot of things, I'm running out of
> > Maybe the rows in the resultset are not unique so that the same record's
> > updated a couple of times ?
> > > As the "Write Conflict" post of 5/21/2000 is no longer available, any
> > chance
> > > of repeating the jist of what it said?
> > > Kate B
> > > > See the post "Write Conflict" on 5/21/2000
> > > > > I am getting the following error in Access 97 when trying to
> > > > > query from a local Access Table joined equally to a linked SQL
> > > > > table with proper permissions:
> > > > > "This record has been changed by another user since you started
> > editing
> > > > > it. If you save the record, you will overwrite the changes the
> > > > > user made."
> > > > > Please help. This is causing major problems for my company.
> > > > > Thanks