Ian Mitchell

[Ian Mitchell]

Have you tried this in eaSheets? We no longer provide support for eaXL, since it was replaced by eaSheets some years ago. Please can you install eaSheets, part of eaTeamWorks, and see if the issue persists. Thanks

[Ian Mitchell]

Sorry about that – this option was not migrated to the last new major version, and you are the first person to spot this!
Function has been put back in v1.5.0.10, now on the website.

[Ian Mitchell]

This usually happens when eaDocX – or any of the eaTeamWorks products – are run on a display which has a resolution gre4ater than 96 DPI. This is usually because it it running on a hi-res laptop, like a Surface Pro, or any other with a 4k screen.
If you either use the machine with a lower resolution, or use it on a separate, normal resultion screen, then it will be OK.
(This is well documented in other forum posts)
Please submit the other issue in a separate post – it is not related to this GUI issue.

• This reply was modified 3 weeks, 6 days ago by Ian Mitchell.

[Ian Mitchell]

happy days

[Ian Mitchell]

By default, eaDocX will use the H1…H9 heading styles as defined in your word document.
The best place to change what each style looks like is in Word: eaDocX does not have many ways to do these changes, as Word does such a good – if confusing – job.
I always find it hard to make heading numbering (like 1.0, 1.3.4.5 etc) work in Word, but if you get it right in Word, then eaDocX will use those H1…H9 which are defined in Word.

[Ian Mitchell]

The key DLL which must be installed is called Microsoft.Office.Interop.Word.dll.
If this is not installed on your machine, then eaDocX will never work.
I strongly recommend that you do NOT just copy this DLL from another machine: use the appropriate Microsoft installer. This will make sure that any dependencies which the Interop DLL has will also be installed at the same time.
Please also note that we do not prodvide support for virtualised environments: there are too many of them, and we have no way to test them all.

[Ian Mitchell]

This question has already been answered.

[Ian Mitchell]

Update:
I have added a new function into the next version of Model Expert – to be released in eaTeamworks 1.4 along with lots of other improvements.
This will change the way that Guided Modelling works. It will now be default OFF, so that most users, who probably don’t use MX-GM, will not see a performance loss.
Enabling GM will now be added to the list of things to do when starting to to use MX-GM.

User will still be able to use the analysis and dashboard functions of MX as today.

The setting is per-user, along with all the other user-based settings of eaTeamWorks, so should work ok in virtualised environments.
Thanks for the sugestion.

[Ian Mitchell]

Named Ranges are an Excel feature, which we used in the old ‘eaXL’ product, which was replaced in 2023 with eaSheets. This uses a non-Excel spreadsheet, but which can inport from- and expert to- Microsoft Excel. Named Ranges are not supported in eaSheets.

[Ian Mitchell]

If your normal response time to create a new element is 5 sec, then if you have Model Expert enabled, I would expect the response time to be of the order of 2-3 times as long. This is because, as you correctly said, MX is doing lots of checks when an element is created, even if at the end it takes no action. For users who are not using the full Guided Modelling function, I suggest you switch off MX. Then just enable it if they want to use any of the post-modelling functions, like a meta-model check.
We don’t see this in our testing, as we use only local databases, with fast response times.
Perhaps what we need is some kind of ‘fail fast’ feature, where you can specify, on a per-user basis, whether they are using MX Guided Modelling ( probably with default=no) and cache this setting, so that in general, MX can exit from handling the ‘new element’ event without any more database calls.
I am back in the office in around 10 days, so I will look into this as a priority.
Thanks
Ian

[Ian Mitchell]

Hi Rodney,
What version are you using?

[Ian Mitchell]

Thanks for the update.

[Ian Mitchell]

The current version of eaSheets in eaTeamWorks no longer supports the idea of Named Ranges – these were an idea from the days when we used Excel. I guess you must be using quite an old version of eaDocX if it still has Excel support – we discontinued this a few years ago.
You can either continue to use the old version on an ‘as is’ basis, or get the latest eaSheets product, delivered via eaTeamWorks. This is the only version we support.
Thanks
Ian

[Ian Mitchell]

Yes, that eaTeamWorks version is compatible with EA 17. It’s the EA version we run in our test environment.
The challenge here is that when eaTeamworks creats the correct menu items for a right-click, It go into the repository, and we don’t know exactly what we will find there. In your case, something which EA doesn’t like.
I have added some more error checking into version 1.3.7.10, which is now on the website.
This isn’t the smartest way to fix it, but it might work.
If not, I may ask you to try and create the smallest possible repository which still shows the error, then I cna see what EA doesn’t like.
So please, if you can try this new version, let me know what happens.

[Ian Mitchell]

Somehow the Profile and the document have got out of synch.
This error happens when eaDocX looks through the document to find all the eaDocX sections (the bits which start and end with the pink text), but when it looks into the Profile, it can find anything about that section.
Best plan is to delete the section manually from the document (select text from BEFORE the pink bits, to AFTER the end of the ‘end’ pink bits, and delete that from the document. Don’t worry, all the content comes from EA, so you will not lose anything.)
Then just add back a new section, in the right place, and re-generate.

[Author]

Posts