Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: yonatan.lehman on September 06, 2022, 10:19:42 pm
-
Hi
We're about to jump from EA14 + Eapx file to EA16 + SQL server
1) Are there any issues with mixed usage of E14 and EA16 (some users might stay with EA14 initially)
2) Any tips or warnings about making this double move ? (version and local to server)
Thanks
-
Wait until the next version of v16.
The current version (1605) has a very annoying bug where diagrams are sorted under packages in the project browser.
So if you have a package with a few diagram, and also a few package, you'll look track of the diagrams really quickly.
The bug is reported, and I'm expecting it to be fixed in the next release.
I'm holding off on upgrading my clients until this is fixed.
With regards to the move to SQL Server, make sure the communication between your Database and your EA clients is as fast as can be. If not you'll get a lot of complaints about the performance.
A lot of my clients have opted for a Remote Desktop/Citrix solution for exactly this reason.
If you have users working from home, connecting via a VPN, connecting through PCS might help a bit, but probably not as much as with the RDS/Citrix approach.
Geert
-
Hi Geert,
Am I correct to assume that this very annoying bug is a Sparx EA bug and not a Pro Cloud Server bug? In other words, would it be possible to upgrade Pro Cloud Server to v5 and keep using Sparx EA v15 until this is fixed?
M
-
Hi Geert,
Am I correct to assume that this very annoying bug is a Sparx EA bug and not a Pro Cloud Server bug? In other words, would it be possible to upgrade Pro Cloud Server to v5 and keep using Sparx EA v15 until this is fixed?
M
It's definitely an EA client bug. I don't see why it should impact Pro Cloud in any way.
I'm guessing Pro Cloud Server to v5 is compatible with EA v15, but you might want to doublecheck to be sure.
Geert
-
Thanks Geert, the following https://sparxsystems.com/forums/smf/index.php/topic,47101.msg274960.html#msg274960 (https://sparxsystems.com/forums/smf/index.php/topic,47101.msg274960.html#msg274960) unofficially confirms backward compatibility. Unfortunately, there is no official confirmation from Sparx.
-
Something to consider is 32-bit vs 64-bit and knowing what edition of MS Office you have installed.
We tried 64-bit but it wouldn't open eapx files. Turned out our IT Dept had installed MS Office 32-bit. Thus we needed to go back to 32-bit edition to open eapx files (MS Access).
-
I'm not sure if the version of MS Office has anything to do with it.
AFAIK EA 64-bit can't work with .eapx files, period.
Geert
-
EAPX files are not really too much of an issue for us as we use a SQL Server database as our backend repository (and, if we need local repositories, I personally think SQL Lite is a better option).
Besides, we are also going to keep v15 installed in our laptops for some time.