Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - kepNCI

Pages: 1 2 [3] 4 5 ... 9
General Board / Re: Updating package with orher project package
« on: September 21, 2012, 11:31:20 pm »
Thanks so much. Never donned on me to look at version control, but it makes perfect sense.  I started to read up on it and one of the first things it states is that you must have a third party version control system.  So, I am interested in your comment that sounds like you can use version control without a third party package. Anything special you must do in the setup?


General Board / Updating package with orher project package
« on: September 21, 2012, 03:59:35 am »
- Export Package from Proj A to XML
- Import XML Package into Proj B
- Make updates to package in Prog B
- Export package from Proj B to XML

I now want to import the package back into Proj A, effectively updating the package with the changes made while in Proj B.
EA will not allow me to import it back, since it already exists. Appears only choice is to either:
1) Delete package in Proj A and the import the XML
2) Import the XML, stripping the GUID

In either case I loose all links/associations to elements in other packages of the project.
Is there a way to copy a package from a project to another, make updates, move package with updates back into initial pacage while keeping all links and associations?

In case you wonder what I am really trying to do...
I had created data models for all of our production databases via EA re-engineing in an EAP project. I then exported/imported the data models to a SQL server project that is not connected to our production network.  The SQL Server project is a large repository project that not only contains data models, but also has packages that document the production applications, physical devices, enterprise/network topologies, etc.
The data models on the repository are linked to other packages as well as in virtual document definitions. In addition the tables and fields have many notes entered thus enabling a more detailed data dictionary.
It has been several months since the models were re-engineered. I now want to go back to the production EAP project and do another re-engineer so that I can capture any changes. So I exported the data model packages from the SQL Server Repository project and imported them into an eap project located on prpoduciton. I then re-engineered all of the data models. Now I need to take these updated data models and effectivly update the models on SQL Server repository project.

The only way I can think to do it is to transfer the entire SQL server project to an EAP file (DBMS to EAP). Copy the eap file onto the production enviroment. Perform the re-engineering. Copy the eap file back to the supporting enviroments and transer the EAP file back to the SQL Server Repossitory (EAP to DBMS).  I think this would preserve the GUID and this the links/associations.  I was hoping to somehow only work with the Data Model package.

General Board / Re: Import DB schema from ODBC source
« on: January 13, 2012, 06:39:42 am »
Is the same true for a deleted field within a table?  

Bugs and Issues / Re: MS Access 2013 and EAP files
« on: June 17, 2015, 01:32:59 am »
I entered this issue as a bug report. Here is SPARX's reply:

The purpose of the JET 4 button is to provide support for JET 4 projects. It doesn't and isn't intended to change the format of any JET files, including new projects.

FACT: In order to use MS Access 2013 to read an eap file, the file must be JET 4.0 format. MS Access 2010 and 2007 can read both 3.5 and 4.0 JET format.
Based upon SPARX comments and experimentation, I believe the following to be accurate:

Enabling the "Use JET4 option" only is functional (at least from a user's perspective) when you have already created a JET 4.0 formatted eap file.

Out of the box, EA can only create new eap projects in 3.5 JET format. To make it 4.0 format, user must open EA with the "Use JET4 option" already enabled, then open the existing 3.5 JET formatted eap project, then use database management/file to file transfer (eap to eap) to replicate the database. The replicated database will be in JET 4.0 format. NOTE: From that point on, make sure you always have the "Use JET4 option" enabled or you will no be able to open the 4.0 formatted project.

In order to have EA create 4.0 eap projects when creating a new eap file, you have to fudge the EA program file by:

- downloading the EABaseJET4.eap file from SPARX.
- overwrite the EABase.eap file in the EA program folder with the EABaseJET4.eap

When creating a new eap file, apparently EA will always start with the EABase.eap file, thus what ever format EABase.eap is, that is what the new project will be.  Beware, that if you change the EABase.eap file in the prgram file to the 4.0 format and then run EA with the "Use JET 4.0" NOT enabled (as if to create a 3.5 format), EA will throw several errors and eventually abort.  Basically EA cannot support the creation of new EAP databases in either 3.5 or 4.0  Must be one or the other depending upon the format of the EABase.eap file the program directory.

Personal comment:
I still see it as a bug or at the very least, poor design. In my opinion, EA should be able to create a new eap file in either 3.5 or 4.0 format. I would think that would be easy to code by having both base files in the program file and using the "Use 4.0 JET" option to determine which to use.
In the current design, I an not really sure what the purpose of the "Use 4.0 JET" option is. I would think EA would determine the format version of the eap file by looking at the file instead of a use-enabled option. But apparently the truth is a mixture. Regardless of the value of the "Use 4.0 Option", if the eap file is 3.5, EA is happy and continues supporting the 3.5 format. If the "Use 4.0 Option" is enabled and the file is 4.0 format, again EA is happy and continues supporting the 4.0 format. However if the "Use 4.0 Option" is NOT enabled and the file is 4.0 format, EA throws an error that it is not a recognized file format.

I will continue to be amazed at the functionality of EA and can understand bugs that do not get fixed immediately, but in this case, SPARX has disappointed me.

Bugs and Issues / Re: MS Access 2013 and EAP files
« on: June 11, 2015, 06:31:17 am »
Yuk. Doesn't that mean that I have to replace the EABase.eap file with EABase_JET4.eap file every time I install a new EA version?  

I would have thought that EA install would have both base files in the program file and then use the "enable 4.0" option to determine which one to use when creating a new eap project.

Bugs and Issues / Re: MS Access 2013 and EAP files
« on: June 11, 2015, 04:41:10 am »
I partially answer my own question (with an assist from Elpis).

I now believe the following statement is true:
MS Access 2013 can read an eap file if it is JET 4.0, but cannot read Jet 3.5 eap files.  One must convert the 3.5 eap file to a 4.0 eap file using the transfer file to file function where the target is a Jet 4.0 file.

My mistake: I was assuming that if I had the 4.0 option set and created a new eap file, that it would be a JET 4.0 file.  
NOPE. EA was still creating a 3.5 Jet file. So, Instead of creating a new file with the JET 4.0 option set, I instead downloaded the "" file and used the contained file "EABase_JET4.eap" as the target.   Thus ensuring the target was a Jet 4.0 eap file.  Now Access 2013 can read it.

Now my question is:
How do I make EA create Jet 4.0 formated eap files when I create a new eap database?

Bugs and Issues / Re: MS Access 2013 and EAP files
« on: June 11, 2015, 04:08:15 am »
Thanks Elpis

I did know that, but I am not convinced I am creating a 4.0 jet file.

I usually run with the Jet 4.0 option enabled. Thus I was thinking that all new databases that I create would be JET 4.0 format.  So I tried a little experiement...

1) I created a new EAP database, selected class as the model and the resulting eap file was 1186 Kb.

2) I then disabled the Jet 4.0 option, restarted EA and created another new eap database, again selecting class as the model. The file size was also 1186 Kb.  I thought the Jet 4.0 file size should be larger.

Also, if I open either file with Access 2010, it says it is an Access 97 file format.  

So maybe my issue is that I have not been able to create a Jet 4.0 eap file.  

Bugs and Issues / MS Access 2013 and EAP files
« on: June 11, 2015, 01:24:39 am »
I have read several posts about trying to use MS Access 2013 to directly read an eap file, but I could not find a definitive answer.

Is this a correct statement?:
Access 2013 cannot read an eap file unless you first convert the file via Access 2007 or 2010 to an accdb file, which then renders it unreadable by EA. Therefore MS Access 2013 and EA are not compatible. i.e., they cannot both read/update the same file.

I have no problem when using MS Access 2010. I must assume that because MS Access 2013 dropped support for JET 3.5 it cannot read eap files, even if I had the jet 4.0 enabled within EA.  

I also tried to use MS Access 2010 to convert the EAP file to accdb format, but then EA cannot read it. Thus I have come to the conclusion as stated above.

Bugs and Issues / Re: Diagram "Fit to Screen" not working well.
« on: May 08, 2015, 06:40:22 am »
I had tried before posting using search:
Fit to Screen
on all forums for all time, but nothing really popped up.

Bugs and Issues / Re: Diagram "Fit to Screen" not working well.
« on: May 08, 2015, 05:17:06 am »
Ctrl-A did not show up any hidden elements, so...
Guess its cause #2, so to speak.

Bugs and Issues / Diagram "Fit to Screen" not working well.
« on: May 08, 2015, 02:59:55 am »
What influences how EA displays a diagram when one clicks "Fit to Screen"?
I have an issue that the "Fit ti Screen"is either not displaying all of the diagram or in the other case, displaying it much smaller that it actually is.

I have two very similar diagrams (both are network deployment diagrams). Both diagram properties are the same, i.e., 11x17 Landscape, Scaled=None. I also have them set so that I see the page boarders.

One has all objects within a 5 row x8 column page grid while the other is slightly smaller (4 row x 6 column pages).

When I display the 5x8 and click "Fit to Screen" on a 1080x1680 monitor, it displays 10 rows x 11.5 column pages (as if there were some invisible oblject that it wants to include that sits way outside the visible objects within the 5x8 pages. Its even worst when I display it on the laptop's 1200x1920 screen, in that it displays 13 columns. I thus have a lot of empty pages and the actual 5x8 pages are about 1/3 the size they should be.

The other diagram is just the opposite. Instead of displaying the 4x6 pages on the 1080x1680 monitor, it displays 4.5 rows x 6.25 column pages, thus cutting off objects in the 6th column. However when I display it on the laptop's 1200x1920 screen, it displays just about right.

Is there anything I can do that may make EA reset what it thinks the diagram's "Fit to Screen" displayed width and height are? Or is this an issue (a.k.a. bug) within EA in determining the active monitor's display properties.  

I have had this issue across multiple EA releases, but I am currently using 12.0.1212.  

Bugs and Issues / Re: order of elements in documentation generator
« on: March 03, 2015, 06:30:21 am »
I'm guessing that since all of the elements in my diagram are links to instances or package elements defined in other packages, EA does not attempt to make any tree order and just uses name.  

If that is the case, I would think it would at least attempt to group any   embedded or nested elements by parent.  

Bugs and Issues / order of elements in documentation generator
« on: March 03, 2015, 06:19:37 am »
The default Order for Packages, Elements and Diagrams in the Generate Document/Options is set to Tree Order/Ascending.

Using the above defaults, why when I include the elements of a diagram in the template (Sections/Package/Diagram/Element), they are always always sorted by Name?

v12. 1207

Bugs and Issues / Re: Red Exclamation in Project Browser
« on: February 25, 2015, 02:11:07 am »
Forgot to mention: security is NOT enabled.

Bugs and Issues / Red Exclamation in Project Browser
« on: February 25, 2015, 02:07:54 am »
I am working on an eap project file on my pc, thus I am the only user.
In the project browser on just one of many packages, I see a red exclamation icon in between the package icon and name.
Other posts state that this indicates the package is locked by another user.  How can that be when I am the only user accessing the eap project?
Is there another reason that triggers the red exclamation?

Restarting EA clears the red exclamation.

(Note: never saw this before r12).

Pages: 1 2 [3] 4 5 ... 9