Ahh! Replication Mess!

[ebeb]

I can't say nobody told me (thanks to Geert), but I was hoping for a normal use of eap replication I won't get into any trouble.

Now I know better.

I just created a replica and worked one day at home in a different package than the other employees. My package is version controlled so nobody could access. That's why I assumed that no conflicts should happen.

Now I know better.

This morning, I synced the DB and I got the cryptic "Resolve Conflicts" window. It told me that in table "package" the GUID "{A34534-343FE-..." has modified. Keep the current value 0 or overwrite by the value 3?  :-?

What the  f***? How should I know what that means? Just chose the latest value.

After that, one whole sub package I created with lots of requirements COMPLETELY DISAPPEARED! Two other packages I worked on were EMPTY!!! That's the worst case scenario! In both replica and master these packages were lost.      

I had to manually import the two empty packages contents from the xml file. I could not manage to recover the one that has disappeared.

The work from one day is lost!  

Now I know better.

To other EA users, I can only say this: Don't use replication!
To EA, I can only say this: Remove the feature from EA!

I already read, that its a Jet feature, not an EA, so if you can't provide a reasonable interface to that feature, don't provide it at all!  

-Jan

[Geert Bellekens]

I'm sorry, I know I shouldn't, but I can't resist:

[size=14]Told you so![/size]

Geert

PS. Jan, I really don't understand why you choose to use replication.
If you have version control you can checkout a package, take it home (offline) edit it, and when you come back in check it in again.
You already had all the tools to work in a distributed way with the version control... :-/

[ebeb]

I'm sorry, I know I shouldn't, but I can't resist:

[size=14]Told you so![/size]

  Yes you did! Doh...

I really don't understand why you choose to use replication.
If you have version control you can checkout a package, take it home (offline) edit it, and when you come back in check it in again.
You already had all the tools to work in a distributed way with the version control... :-/

Because I though its the right way. I didn't think about using the xmi files... So what do exactly mean?

Using the EAP, checking out a package (which updates the xmi) and then what? Creating a new project and import / edit / export the xmi and then import it back in the EAP?

- Jan

[Geert Bellekens]

Jan,

With the EAP files its even easier.
take following steps:

• Checkout the packages you want to edit at home (as you did before)
• Make a copy of the (shared) eap file and put it on you laptop
• At home start up EA and tell it you are working offline (Project/Version Control/Work Offline)
• Open the eap file at home and edit as usual. (only the checked out parts ofcourse)
• When back at the office just check the packages you have edited back in and do a "getlatest" on the shared eap file.

That should save you a lot of headaches.

Geert

[Eve]

Not to lessen your experience in any way, but using version control with replication would be a fantastic way to cause conflicts and all sorts of bad behavior, since version control deletes a package and recreates it.

[ebeb]

Not to lessen your experience in any way, but using version control with replication would be a fantastic way to cause conflicts and all sorts of bad behavior, since version control deletes a package and recreates it.

really? so:

Remove the feature from EA!