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 - Simon M

Pages: 1 ... 388 389 [390] 391 392 ... 422
At a glance, you haven't specified a valid connector type.

You'll have to modify the code templates...

Look for a %REPLACE(";", "\n")%.

I'd try making it %REPLACE("];[", "]\n[")%.

It is in a tagged value.

Reverse engineer one to see the details.

Sorry, the whole purpose of the encrypted connection string is that admins can give the users that string if they don't want their users to know how to connect to the actual database.

So you'll need to ask your admin for a non-encrypted connection string.

Manfred is on the right track.  GetElementsByQuery takes the name of a search.  You can define a search for almost anything in EA, including Element Type or Stereotype.

Not being able to set a GUID is not related to the .Net wrapper.  It is readonly for .Net because it is readonly for COM.

Automation Interface, Add-Ins and Tools / Re: Source Code Engineering
« on: March 06, 2009, 10:31:44 am »
EA won't pick up the links between tables and classes.

Well said, and exactly right.

The element of a package should never have sub elements.  The elements that a package owns should belong to the packages elements collection.  So you should add your sub elements directly to the package.

I suspect that if EA allows you to add elements to the package element, it will create data integrity issues (regardless of whether the integrity checker picks it up or not.)

But saying that won't really help you.  Maybe if you described a bit more of what you're actually trying to do, I (or someone else) can offer suggestions of other ways to do it.

... my encapsulated object count: Package.Element.Elements.Count is always coming back: == 0.
Use the Package.Elements collection instead.  For a package the Element.Elements collection will always be empty.


The _makeComposite attribute is applied to a metaclass element, not a stereotype element.

Automation Interface, Add-Ins and Tools / Re: Java don't works
« on: February 16, 2009, 08:27:33 am »
The date of SSJavaCOM.dll should be 13 October 2008.

I've got your support request, I'll send you the 834 files via email.

Automation Interface, Add-Ins and Tools / Re: Java don't works
« on: February 11, 2009, 08:24:03 am »
Did you upgrade using the installer of the patch file?

If it was the patch file, did it include the SSJavaCOM.dll file?

What are your SSJavaCOM.dll and eaapi.jar files dated?

Automation Interface, Add-Ins and Tools / Re: Java don't works
« on: February 10, 2009, 08:35:46 am »
Then upgrading to the latest build should help.

Pages: 1 ... 388 389 [390] 391 392 ... 422