Re: Insert Error

• Previous message: DB: "Copying a replicated database"
• In reply to: Dean Turner: "Re: Insert Error"
• Next in thread: Dean Turner: "Re: Insert Error"
• Messages sorted by: [ date ] [ thread ]

Date: Tue, 16 Mar 2004 09:43:19 -0800

(1) It depends -- it may or may not be possible, depending on the situation.
Have you tried outting the proper records back in rather than removing them?

(2) cf: http://trigeminal.com/usenet/usenet009.asp

-- 
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
This posting is provided "AS IS" with
no warranties, and confers no rights.
"Dean Turner" <anonymous@discussions.microsoft.com> wrote in message
news:ab8701c40ad5$0ea458e0$a601280a@phx.gbl...
> Ok, that raises three questions:
>
> 1.) Is there any way to clean up the error?
>
> 2.) How does one go about moving or copying illegally?
>
> 3.) I thought, that the sync process itself would fail if
> you tried to sync to a different db.
>
> Dean
> >-----Original Message-----
> >Hmmm... the only time I have ever seen that before is
> when one of the
> >replicas was moved/copied illegally (so that Jet thought
> the problem was
> >originally from a different database).
> >
> >MichKa
> >
> >"Dean Turner" <anonymous@discussions.microsoft.com>
> wrote in message
> >news:cdad01c40a18$6e085830$a501280a@phx.gbl...
> >> Yes - they are gone from both replicas!!!
> >>
> >> >-----Original Message-----
> >> >Are they gone from both replicas?
> >> >
> >> >
> >> >-- 
> >> >MichKa [MS]
> >> >NLS Collation/Locale/Keyboard Development
> >> >Globalization Infrastructure and Font Technologies
> >> >
> >> >This posting is provided "AS IS" with
> >> >no warranties, and confers no rights.
> >> >
> >> >"Dean Turner" <anonymous@discussions.microsoft.com>
> >> wrote in message
> >> >news:9a1c01c40953$e9606240$a601280a@phx.gbl...
> >> >> The "Replication/Resolve Errors" identifies 38
> errors.
> >> >> Most of the records simply says "Insert".  There is
> no
> >> >> explanation identifying what the error is.
> >> >>
> >> >> I followed the directions and identified several of
> the
> >> >> records.  They were all detail records pertained to
> the
> >> >> same transation master. I had the person whom I
> >> believed
> >> >> caused the error delete the master and its
> >> corresponding
> >> >> detail and then perform a sync.
> >> >>
> >> >> After syncing myself the error count remains at 38
> and
> >> >> the "Replication/Resolve Errors" shows the exact
> >> >> same "Insert" errors.  However, when I follow the
> >> >> directions to identify the error records it does not
> >> find
> >> >> a match.
> >> >>
> >> >> So the master and its corresponding detail are gone,
> >> but
> >> >> the errors remain.  Any ideas of how I can get rid
> of
> >> >> these "Insert" errors records?
> >> >>
> >> >> I am using Access 97.
> >> >>
> >> >> Thanks; Dean
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

• Previous message: DB: "Copying a replicated database"
• In reply to: Dean Turner: "Re: Insert Error"
• Next in thread: Dean Turner: "Re: Insert Error"
• Messages sorted by: [ date ] [ thread ]