Losing objects when synchronizing?

[LarrySkelly]

We've been experiencing issues where objects disappear after a synchronization.  Its getting to a point where I cannot handle the risk of losing parts of our model.

This morning I synced with the master, and I lost most of the attributes off classes on which I had modified an attribute.  I lost all attributes except the ones that had been modified.  They just disappeared and it is going to take some significant time to recreate them.

At this point I am very nervous about using the product with any sort of replication.

Has anyone else had issues with this?

[Tjerk]

Hi Larry,

I've experienced the same, I guess you will find a message on the forum (probably more than 1/2 a year old).

I do not trust the procedure myself nowadays and rely on XMI export & import and using one model with more than one user at the time. Both work up till now.

The replication business is one of MSAccess I believe, so maybe someone (Sparx?) could find out the "rules" of replication with MSAccess and explain the odd behaviour.

Just guessing, maybe it has something to do with systemclocks being out of synch and MSAccess relying on modification timestamp for synchronising?

Greetings,
Tjerk

[kevinimnotspacey]

I don't know, we've lost object references from sequence diagrams using the XMI import/export.  You can probably chalk it up to new users not reading documentation.   At any rate, we've switched to using SQL Server back end and that is very nice, very easy to use.