Ian Mitchell

[Ian Mitchell]

I assume you’re using the ‘Find’ button on the ‘Source Elements’ or ‘Target Elements’ pages in the Manage Relationship Matrix Reports’ form ?

[Ian Mitchell]

Hi – is this still a problem you’d like me to look at?

[Ian Mitchell]

Hi Jan,
I have never tried to do this, and unfortulately I can’t test it as i’m away from my desk for a few weeks (in NZ meeting customers). I’ll be back at the start of March,
Sorry 🙁

[Ian Mitchell]

Which version of EA do you have? Professional or Corporate? This is an EAPX file, so I think it needs Corporate Edition of EA.

[Ian Mitchell]

HI James,
At what point does this message appear? When you try to open the repository in EA?

[Ian Mitchell]

If you choose to print the elements type as ‘Inline’, then choose ‘vertical table’, that should do it. Not sure about printing the ‘notes’ of a TV though….

[Ian Mitchell]

Ok – you lost me at ‘multi-user EAPX’ : this isn’t supported by Sparx, or by us, so sadly you’re on your own. Yes, I know it works – mostly – but these locking issues are what makes it an un-supported configuration.

• This reply was modified 2 years, 4 months ago by Ian Mitchell.

[Ian Mitchell]

Making good progress on the 64 bit version. But EA V16 comes with a new type of DBMS, to testing that as well. There is a V5 64-bit verison now on the website – please try it and let me know how it goes.

[Ian Mitchell]

Hi Steve,
We are still testing eaDocX with QEA files – there are some differences in the SQL they accept, which seems to be different from all other DBMSs.
We are also having other issues with EA V16, so we are planning to do more testing to resolve these issues.
In the meantime, I suggest reverting to EA 15.
Thanks

[Ian Mitchell]

When I look at the error, this is coming from a call which eaDocX makes to Word, so if there is a restriction, it must come from Word.
I have tried to replicate this error, with element names of 256 characters, and it is ok.
Are you still using Arabic characters ? My test envoriment is a simple ENG/UK language.

[Ian Mitchell]

This seems to have become a general-purpose thread 🙁
@Marie – eaDocX does not support arabic text – I have no way to test it, or to debug any issues you have with it, as I am not an arabic speaker – sorry!

[Ian Mitchell]

If you zip the repository, and send it to me via WeTransfer, then I will look at your issue. Send it to ian@eadocx.com

[Ian Mitchell]

It sounds like there is either (a) an issue with the EA content, or (b) eaDocX has found something in the model it doesn’t understand.
If (a) then run the EA Integrity Check (in V15: Configure / Model / Integrity check) which can find errors. If this does not work, then export a large part of your model to an XMI, delete that part of the model, then re-import. This removes all kinds of errors.
if (b) then I can only look into it if I have some sample data to work with.
Thanks
Ian

[Ian Mitchell]

If you can send me a small XMI with the data which makes eaDocX fail, I will have a look at it. The data probably just has a state which I have not seen before.

[Ian Mitchell]

Does this happen for every kind of Quick Document? Or just on one part of your model?

[Author]

Posts