Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: jnrtkm99 on February 25, 2012, 12:15:21 am
-
Getting the above message when trying to create new replica (Tools > Data Management > Manage .EAP File > Create New Replica... )
Have already run 'Make new master' against this model.
Does anyone know of a workaround?
-
Hi, I have exactly the same problem. It seems to be old and rare. Is there now any known solution? I need urgent help. Marco
-
I'm sorry, the only advice I can give you is to avoid the master/replica mechanism at all costs.
Nothing but trouble if you ask me.
Geert
-
Thx for quick answer.
Unfortunately, I have to replicate because sharing a central EAP file produces errors and a colleague must therefore work locally (the others not). Do I have to remove the replication of EAP file before we are working together on a network drive? And are there known issues associated with SharePoint environments? I can choose between both environments (SharePoint, Network-Drive).
Marco
-
If you need to share, switch to a version control system (subversion is still the choice here, but any other will do also). Avoid replicas, this is Mickeysoft scrap at it's best. For all what I heard take a long road to bypass SharePoint as well. It's definitely not a place for EAP files. Using EAP (MS Access) on shared drives is not recommended, unless you have a broadband network (your admins will love ou for that). You should remove replication, though I guess it would be possible to leave it. Just as a guess, it will create a lot of clutter inside and make the DB even more unstable.
q.
-
Marco,
.eap files on sharepoint is a definite NO-GO. It simply doesn't work as it needs to add temporary lock files and stuff like that.
Geert
-
I don't have access to a version control system. So I try to remove replication and share the EAP at a common network drive. Thx for your help so far.
-
Hi,
be careful with a common network share.
I have experienced corrupted repository, more than once.
Helmut
-
Setting up subversion should be a no-brainer...
q.