Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Error #1305 when loading update (replication)
Sun, Jun 15 2008 3:09 PMPermanent Link

ulibecker
Hi,

I just tested the replication feature for the first time.
Everything works fine except the last step: "load updates",

For testing purposes I copied a database and after publishing it, I removed some records
from a table.

After a "Save Updates" I tried to load the update in the copied database. Here I got this
error:

ElevateDB Error #1305 Error loading the updates for the database InformaTest (No row found
in the table Posten with the primary key or unique values of 0)

What am I doing wrong?

P.S. The statement "Load Updates For Database <name>" is not clear for me. Is <name> the
source database or the target database?

Uli
Mon, Jun 16 2008 9:35 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

<< For testing purposes I copied a database and after publishing it, I
removed some records from a table.

After a "Save Updates" I tried to load the update in the copied database.
Here I got this error:

ElevateDB Error #1305 Error loading the updates for the database
InformaTest (No row found in the table Posten with the primary key or unique
values of 0)

What am I doing wrong? >>

This type of error means that you're trying to load an update for a row
where the original row cannot be found in order to complete the update.  Do
you have a primary key defined for the table in question ?

<< P.S. The statement "Load Updates For Database <name>" is not clear for
me. Is <name> the source database or the target database? >>

It's the target database.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jun 16 2008 9:45 AMPermanent Link

ulibecker
Tim,

<<
This type of error means that you're trying to load an update for a row
where the original row cannot be found in order to complete the update.  Do
you have a primary key defined for the table in question ?
>>

Yes, there is a primary key.
Actually I deleted some records in the "source" database (table posten) and expected this
to be replicated after an update of the "target" database.

Uli
Mon, Jun 16 2008 10:44 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

<< Yes, there is a primary key.  Actually I deleted some records in the
"source" database (table posten) and expected this to be replicated after an
update of the "target" database. >>

Yes, that is exactly what will happen if things are done properly.  If you
want to send me an example of what you're trying, I can tell you what the
problem is.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jun 16 2008 10:59 AMPermanent Link

ulibecker
Tim,

<<
Yes, that is exactly what will happen if things are done properly.  If you
want to send me an example of what you're trying, I can tell you what the
problem is.
>>

Ok, I'll send you a mail.

thanks. Uli
Image