🚀 go-pugleaf

Mike,

I've had the same error too. I checked each scheme and the defaults for all
replication schemes and removed any time-stamp priority and it worked fine
since then, if not it might be worth trying all the prirotys as the same and
see if it works.

Steve



"Mike Senkovich" <mikes@decisionsys.com> wrote in message
news:3bec4405$1_1@dnews...
> Hello all.
>
> I am getting an access violation that prevents me from shutting down IB
Repl
> Manager without going to Task Manager and forcing a shut down.
>
> It happens on my PC regardless of what priority is set for the Schema DBs.
> It doesn't happen for all replicated tables.  If I change a single record
in
> a small table (2 fields) and replicate, then close down IB Repl Mgr, there
> is no AV.  It can happen when a simple replication of 1 record is
performed
> in a table (I'm using SQL Explorer for simplicity).  When a record is
> modified in a table that either has many fields (at least 27) that seems
to
> trigger the AV on close.
>
> The schema is set up as an N-Way scenario with just two tables (a source
and
> DB).
>
> I can provide sample DBs (source, target, config) that consistently
> reproduce the error (on my PC, anyway) if necessary.
>
> I can see this AV being a source of frustration for customers since they
> will always be replicating data in the larger tables (and therefore
> potentially always getting the AV when they close the app).
>
> Any ideas or workarounds?
>
> Thanks.
> -Mike
>
>