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 - Geert Bellekens

Pages: 1 ... 3 4 [5] 6 7 ... 548
Bugs and Issues / Re: Files on Sharepoint
« on: June 14, 2018, 04:41:14 am »
You should never put .eap files on sharepoint.

An .eap file is basically an Access database with another extension.
When using it tries to create a temporary lock file, which sharepoint doesn't allow.


General Board / Re: unchecked "Show Namespace" as default?
« on: June 13, 2018, 07:42:06 pm »
Have you tried the template package?


Automation Interface, Add-Ins and Tools / Re: Help with collections
« on: June 12, 2018, 04:53:32 pm »
Hi Dana,

EA.Collection is not a "regular" collection type.
It can be used to iterate elements in EA (e.g. Element.Attributes) or to create new objects in EA (e.g. set myNewAttrbute = Element.Attributes.AddNew("attributeName", "string))

You cannot use it as a general purpose collection type.
Instead you can either use an array (which is often annoying since it has a fixed size) or use a .Net ArrayList.
To create a new ArrayList use:

Code: [Select]
dim myList
set myList = CreateObject("System.Collections.ArrayList")


Latest information:
This appears to be a bug when one of the packages is selected to "Exclude From Generated Reports".  The random generation appeared when my 2nd package was excluded.  When I un-checked the exclusion box the issue went away.
Have you reported the bug to Sparx?


Have been running a mix of 13.5 and firstly 14.1420 and then 14.1421 for the last week or so and haven't encountered issues so far.

Same here, no issues.


General Board / Re: SQL Join problems
« on: June 12, 2018, 04:27:52 pm »
There are a number of macros that you can use in these situations.
#PACKAGEID# in this case.

See for more info


General Board / Re: SQL Join problems
« on: June 09, 2018, 02:58:40 am »
this works:
Code: [Select]
SELECT req1.NAME AS From_Name, req1.NOTE AS From_Notes
FROM  ( t_object Req1
LEFT JOIN t_connector trace ON Req1.object_id = trace.start_object_id)

Start from there and then add more joins one by one, making sure your syntax stays correct.


Have you thought of importing the MDG into the model?
Your trial project could then import the trial MDG, and everyone that connect to that model has the correct version of the MDG without having to synchronize paths or anything.


General Board / Re: Import Database Schema and Foreign Keys
« on: June 08, 2018, 03:53:59 pm »
I don't think so.

What you are doing seems a bit strange to me.
By reverse engineering you create a model that is 100% the same as your physical database.
By adding FK relations that aren't there you are making a model that is no longer representing the physical thing.
What is the sense of having a physical model when it doesn't represent the actual physical thing, but rather the physical thing and then some other stuff that isn't really there.

I think you should either:
- forward engineer the foreign keys so they are in the database as well and will be there when you reverse engineer
- create these "foreign key who aren't really foreign keys because they don't exist in the database" relations on a logical model rather then on a technical model.


General Board / Re: SQL Join problems
« on: June 08, 2018, 01:21:50 pm »
Hi Sean
- t_connector1 does not exist. Use aliases like so
  t_connector c1 on c1.Start_Object_ID = t_object.Object_ID (I always use aliases for all my tables, much easier)
- I you are using a .eap file you'll have to use parentheses for your joins
something like
Code: [Select]
from (((( t_object o
inner join t_package package on o.package_id = package.package_id)
left join t_package package_p1 on package_p1.package_id = package.parent_id)
left join t_package package_p2 on package_p2.package_id = package_p1.parent_id)
left join t_package package_p3 on package_p3.package_id = package_p2.parent_id)

- full outer join why would you want to use a full outer join? Do you want to make a list of all elements and all connectors? I have never needed a full outer join, I would have to look up the syntax for that.

In general the best approach to this is to start small and then expand you query bit by bit. That will allow you to identify the syntax errors quite easily.


Suggestions and Requests / Re: New standard element property: ID
« on: June 06, 2018, 01:58:47 pm »
What is your reasoning for this not being a tagged value?

I agree, that is exactly what tagged values are for, to extend the standard properties with your own.


General Board / Re: Re-use existing MDG diagrams within a custom MDG?
« on: June 05, 2018, 10:13:51 pm »
I wouldn't be 100% the same as a regular SysML diagram, but I guess it would probably be close enough as the main purpose for a diagram type is to link it to a toolbox.


Bugs and Issues / Re: MDG Technologies overwrite local scripts
« on: June 05, 2018, 09:54:35 pm »
Hi Benno,

I think your observation was a bit skewed as you were discussing a high profile bug in a very new version.

I usually post both on the same time.
Posting on the forum might help other users who have the same problem, and sometimes you get a workaround that way as well.
I don't think it will make much difference to the way the Sparxians deal with it.


Hi Dana,

The documentation is found in the help file around here:
Browsing through the API will get you much information, but not all.

To supplement the official documentation you can read Thomas Kilians books, especially Inside and Scripting.

Other then that I usually look in the database where I can find a specific piece of information. After a while you get a "feeling" for how EA works and it will get easier.

If I really can't find I sometimes use SQL Profiler on my SQL Server model and manipulate the information I'm after.
The profiler will record all SQL queries on the database, so hidden in there I always find what I need.

with regards to the tagged values on a package, they are stored in EA.Package.Element.TaggedValues
(EA.Package is a bit peculiar as it is both an EA.Package as an EA.Element at the same time; except for root packages that is)

As for the relation between an instance and it's classifier, that is stored in the field EA.Element.ClassifierID on the instance.


Pages: 1 ... 3 4 [5] 6 7 ... 548