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 - Richard Freggi

Pages: [1] 2 3 ... 13
1
All fixed now, thanks everyone for practical and moral support!

A final issue I had to resolve was that Firebird was really picky with my Memo fields and would fail some sting concatenation operations (||).  I tried casting Note fields to VARCHAR, TRIM and everything else, but I only SUBSTRING can force Memo fields to work reliably with ||.  So I had to set all memo string manipulation to 

 || SUBSTRING((Note field blah blah) FROM 1 FOR CHAR_LENGTH(Note field )-1)  ||

After dropping the final character in the note, the note displays in full, so there must have been some garbage ASCII in the last byte, many possible causes - maybe the transfer to Firebird, or the fact I have pasted into the Notes from different languages so double byte may have screwed something up.

Anyways I'm happy as!  Thanks everyone.

2
This is crazy.  All columns failing the JOIN are related to custom tagged values I added to the UML types before the transfer to feap.
If I remove the column alias statement on my query (select columname AS displayname) then the query runs but the JOIN fails to filter any rows (blank result)
I can see some garbage characters with umlaut in the raw column names if I SELECT * from t_objectproperties

Weird stuff.  Fortunately I am not using these tagged values yet, so will just delete and recreate them.

Ps.s. Geert thanks for your advice, tried it did not help in this case, seems to be the garbage tagged value names that cause the errors (mismatch of column names in the query causing ADOB error)

3
Thanks Sunshine I didn't know that.  I thought the menu reset the GUIDs.

Happy to report all smooth sailing, except for one glitch.  This JOIN to query tagged values of Memo type was working in Access, but I get an error " ADOB.Fields Item cannot be found in the collection" in Firebird.  It actually works if I remove op.8 and following JOINs.  Any ideas?

-- ACCESS CODE
FROM ((((((((((((t_object
LEFT OUTER JOIN t_package ON t_object.Package_ID = t_package.Package_ID)
LEFT OUTER JOIN t_objectproperties op1 ON (t_object.Object_ID = op1.Object_ID AND op1.Property LIKE ('*Process*')))
LEFT OUTER JOIN t_objectproperties op2 ON (t_object.Object_ID = op2.Object_ID AND op2.Property LIKE ('*System*')))
LEFT OUTER JOIN t_objectproperties op3 ON (t_object.Object_ID = op3.Object_ID AND op3.Property LIKE ('*Variance*')))
LEFT OUTER JOIN t_objectproperties op4 ON (t_object.Object_ID = op4.Object_ID AND op4.Property LIKE ('*Remark*')))
LEFT OUTER JOIN t_objectproperties op5 ON (t_object.Object_ID = op5.Object_ID AND op5.Property LIKE ('*Action*')))
LEFT OUTER JOIN t_objectproperties op6 ON (t_object.Object_ID = op6.Object_ID AND op6.Property LIKE ('*SME*')))
LEFT OUTER JOIN t_objectproperties op7 ON (t_object.Object_ID = op7.Object_ID AND op7.Property LIKE ('*riorit*')))
LEFT OUTER JOIN t_objectproperties op8 ON (t_object.Object_ID = op8.Object_ID AND op8.Property LIKE ('*implementation constraint*')))
LEFT OUTER JOIN t_objectproperties op9 ON (t_object.Object_ID = op9.Object_ID AND op9.Property LIKE ('*implementation reference*')))
LEFT OUTER JOIN t_objectproperties op10 ON (t_object.Object_ID = op10.Object_ID AND op10.Property LIKE ('*implementation task ID*')))
LEFT OUTER JOIN t_objectproperties op11 ON (t_object.Object_ID = op11.Object_ID AND op11.Property LIKE ('*security requirements*')))


-- FIREBIRD CODE
FROM ((((((((((((t_object
LEFT OUTER JOIN t_package ON t_object.Package_ID = t_package.Package_ID)
LEFT OUTER JOIN t_objectproperties op1 ON (t_object.Object_ID = op1.Object_ID AND UPPER(op1.Property) LIKE ('%PROCESS%')))
LEFT OUTER JOIN t_objectproperties op2 ON (t_object.Object_ID = op2.Object_ID AND UPPER(op2.Property) LIKE ('%SYSTEM%')))
LEFT OUTER JOIN t_objectproperties op3 ON (t_object.Object_ID = op3.Object_ID AND UPPER(op3.Property) LIKE ('%VARIANCE%')))
LEFT OUTER JOIN t_objectproperties op4 ON (t_object.Object_ID = op4.Object_ID AND UPPER(op4.Property) LIKE ('%REMARK%')))
LEFT OUTER JOIN t_objectproperties op5 ON (t_object.Object_ID = op5.Object_ID AND UPPER(op5.Property) LIKE ('%ACTION%')))
LEFT OUTER JOIN t_objectproperties op6 ON (t_object.Object_ID = op6.Object_ID AND UPPER(op6.Property) LIKE ('%SME%')))
LEFT OUTER JOIN t_objectproperties op7 ON (t_object.Object_ID = op7.Object_ID AND UPPER(op7.Property) LIKE ('%PRIORITY%')))
LEFT OUTER JOIN t_objectproperties op8 ON (t_object.Object_ID = op8.Object_ID AND UPPER(op8.Property) LIKE ('%IMPLEMENTATION CONSTRAIN%')))
LEFT OUTER JOIN t_objectproperties op9 ON (t_object.Object_ID = op9.Object_ID AND UPPER(op9.Property) LIKE ('%IMPLEMENTATION REF%')))
LEFT OUTER JOIN t_objectproperties op10 ON (t_object.Object_ID = op10.Object_ID AND UPPER(op10.Property) LIKE ('%IMPLEMENTATION TASK ID%')))
LEFT OUTER JOIN t_objectproperties op11 ON (t_object.Object_ID = op11.Object_ID AND UPPER(op11.Property) LIKE ('%SECURITY%')))

4
Success!  Integrity check before transfer (minor issues corrected: datatype mismatch on some elements), reset GUIDs after transfer, integrity check again (no issues found), then everything works including no Primary Key error message when creating new elements!  Thank you everyone!

5
Hi Paolo I thought about resetting, had not made up my mind, but will do it based on your prompt

6
Update: after rebooting I got the same error message: the first new element I created caused a "primary key" error message to appear on EA; everything else was OK (no issues with repeating tagged value).
Note that I ran a project integrity check before transferring eap to feap, after opening the feap and again after the error message appeared.  All 3 integrity checks showed no issues.
So it may be a bug or some quirk of Firebird.

7
Thank you Geert I thought it may be a possibility but the user manual seemed to say that both eap and feap can be saved via the Save as menu.  Thanks for clarifying!
I'm rebooting everything and retrying from scratch, we'll see how I go this time...

8
Huh??  I created a brand new feap firebird project in V13 and it also has 'Save as' grayed out. Is the lack of 'save' a feature of Firebird file repository?  Is it normal behaviour? 

'Save' and 'Save as' are always available in all my eap models.

9
I downloaded V15 and the transfer to Firebird feap worked fine.  I checked file integrity before transfer.
I re-opened the Firebird file project using my own V13, everything including diagrams was fine.
I tested adding an element to a package: got an error message "Primary key something" .
I added a tagged value to this new element: it showed duplicate in the tagged value window.  I deleted both tagged values, recreated a new one and this time it created OK
I tried to save the feap model: "Save as" is grayed out an unaccessible in menu of my V13.  No 'Save" menu.  I tried CTRL-S.
I added another element and a tagged value to it.
I closed EA, then restarted and checked the added elements: the first one was gone, the second one was still there. 
Very troubling for a mission-critical model.  Any suggestions?  Would resetting GUIDS help?  But why no save menu?

Thanks for any help!

10
Thanks for confirmation Geert.  So seems like it's a license issue.  If no other workaround, I'll download an evaluation copy of V15 corporate, transfer the model, then reopen with my V13. 

Would there be any backward compatibility problems if I did that?  It's a critical model so I can't afford any data corruption/crashes etc.

p.s. When I evaluated EA I could not find reason to go beyond Professional... I need the model file on my own hard disk thank you very much, plus not enough skilled UML people around to use the collaboration features.  Visio for colorful artwork is seen as the gold standard of professional excellence (bonus points if you use Powerpoint).  But I digress.

11
I have a large project which contains 3 models on a file-based repository in my computer.  It's Access 3.5 (Sparx default).  My EA is version 13 build 1310 Professional.  Windows 10 professional.
I want to transfer the whole project to Firebird file repository.  The manual and this forum says to use Configure > Model > Transfer > Project Transfer in the ribbon menu.  But I don't have any Project Transfer menu!  My transfer menu has a grayed out "Shared repository" and usable "Export reference data", "Import reference data" menus.  Nothing else.
I checked in Options etc. and no menus are disabled.  As far as I remember I am using all default settings in this EA instance.
The "Check integrity" ribbon menu has a "Manage Firebird" usable option.

Can anyone help me understand how to run the transfer?  Thanks!

12
I may be stating the obvious but can't you just use the diagram menu to hide methods (triggers) and datatypes?  And show relationships as UML instead of IE notation.  If you need to convert the physical model to a higher abstraction logical model (with different classes, associations, generalizations etc.) then the only thing that works is manually redesigning the higher abstraction model based on the physical one.  There's a lot of subjective decisions and modeler style/perspectives that go into the abstraction, so I've never seen it automated.

13
General Board / Re: Export diagrams to PlantUML
« on: November 07, 2019, 11:40:14 pm »
Eclipse Papyrus UML modeler has a few bugs and the usability and user interface are not great.  But it's the best truly UML, truly open source tool.

14
You could use a FEAP rather than an EAP.
But be careful, there are gotchas with these such as not being able to live on a network drive, and being case sensitive.

Thank you, I am actively looking for more gotchas and pitfalls before I make the switch, I am in the middle of major project and can't afford any big surprise... don't want to just swap the warts of Access for another set of warts.  Any more insight, please share!

15
Version 13.10.  The manual says that an auto name/numbering with "Apply on creation" should work for new elements created in diagrams or in project browser.  However: first set auto numbering for interactions , then in project browser create a use case, then right click - Add - Interaction - with sequence diagram.  The newly created interaction is not auto named.
Is there a workaround or can we get a bug fix?  Or has this been fixed in later releases.

Pages: [1] 2 3 ... 13