Adrian Support

[Adrian Support]

Hi Werner

I must assume that they have a local language version of Excel or the Multilingual User Interface Pack for your version of Office.

Also the origins of Excel and Word were different and this still shows up in their API’s so I’m not totally surprised.

Ideally I can configure a non-English system and produce the same error.

I’ll do my best to resolve in a timely manner

BR

Adrian

[Adrian Support]

Hi Werner

Thanks for this it is really helpful.

It looks like an Excel process was created OK but then it complains about adding a workbook – not what I expected at all.
It indicates that the library it is trying to use is incompatible.
I’ve found some information on the Microsoft site (if your interested!! http://support.microsoft.com/default.aspx?scid=kb;en-us;320369)

Briefly looks like this is an Excel bug – quoting MS

“If the client computer runs the English version of Excel and the locale for the current user is configured for a language other than English, Excel will try to locate the language pack for the configured language. If the language pack is not found, the error is reported. ”

I’ll look at this in more detail and review solution.

Strange that with all the licenses we have sold in non-English countries we haven’t seen before! I assume most have used their local version of Excel so we haven’t seen this issue.

Hopefully back to you soon.

BR

Adrian

[Adrian Support]

Hi Werner,

Think I have found a possible cause of the problem you observe.

To check this I have produced a simple test application which I would ask you to run and check the results – there is an executable and text file with instructions in the attached zip.

As it says in the instructions – please ensure that you do not have any other instances of Excel running when you run the test application – and then if you could send the results back as per the notes that would be great.

You will see that if you can create an instance of Excel by pressing the button create then I have a solution for you 🙂

Any questions please ask.

BR

Adrian

[Adrian Support]

Hello Werner,

I have tried to reproduce your error without success although we don’t have a Windows 7 Enterprise edition to hand to test against the rest of the configuration is the same. FYI: the errors you are getting relate to some exceptions when we try to open Excel. So possibly need to add some instrumentation to get more detail from a small area of code.

But to start with a few more questions, if I may:

1. Can I verify that the version of Office 2007 is a full installation of Excel and not the ClickToRun version – we know there are problems with ClickToRun as Office may not have installed all the bits we need. We need to confirm that Excel is fully installed and accessible.

2. Do you get the same results regardless of how you try to open Excel e.g. if you use select a package in the project browser | Right click | Extensions | eaDocX | Open in Excel do you get the same errors

3. You say that you are getting the error on other machines – can you confirm that they are all the same configuration

We will update eaXL with some additional instrumentation ready to enable us to perform more checks should that be needed.

Regards

[Adrian Support]

Hi,

I understand your Use Case.

We are keen to offer different options to output other information for elements, however one issue with Excel is that if we output information over more than 1 row we need to ensure there is a mechanism to ensure that we (internally) and you (the users) understand which element the attribute etc relates to. Hence the reason for including summary cells.

It is all too easy to lose context as there is always the risk that a user does some manipulation on the rows and the context could be lost – is this a risk that would be acceptable?

Other options we have considered is adding a column that displays the attribute(etc) owner?

Comments/thoughts always welcome on what and how you would like to see the information.

Thanks and regards

eaDocX support

[Adrian Support]

Hi Stefan,

You’re correct in that having consolidated the attributes into a summary we no longer have the links to the underlying information for each attribute (same for other summary items). Not least a view on how to display if we retain the information for a class element within a single line.

If fact, you have highlighted an example for which outputting an attribute per a line would allow us to display the relevant related information.

We are thinking about it however, as per my previous note, it is about how best to represent this within Excel. We have some ideas, however as always we need to consider how it would be presented in a way that is useful. A simple way would be to output multiple lines for the class element (other elements as well) – 1 for each attribute /operation/etc and rely on the user i) being clear about what they are asking to be output and ii) being careful if they make changes which they may wish to import.
All possible but …

What do you think?

Regards

Adrian

[Adrian Support]

Hi Stefan,

eaXL allows you to export attributes / method etc from a class and other elements where they exist.

To output them:

1. Within the “Columns” tab select “Display Compound Attributes” – that will then include additional items in the columns check list box

2. Select “Attribute Summary” for attributes or “Method Summary” for operations – or any of the other summaries that may be of interest.

Attached is a screen shot illustrating the output of a simple class with 2 attributes and 1 operation.

At present we only output the Compound Attribute items as a list within a single cell; not import.
We have not decided if, and how best, we could output 1 attribute per a line whilst ensuring integrity within Excel. And of course if there is a demand for such a feature. Your comments welcome.

I hope that helps – any further questions do ask.

Regards

Adrian

[Adrian Support]

Hi Andy,

Aware of some issues with terms in that EA appears not to do a refresh as it adds terms to the model, i.e. it is caching them and so they do not appear in the database immediately. We think we have a workaround but want to test to ensure reliable; if so this will be included in an update.

Hence interested in your case – so to check the exact sequence events – let me sumarise:
1. You open (new?) model
2. Add 3 terms ABC, DEF, GHI
Questions 1:
– if you run eaDocX only DEF is output?

Question 2:
– if you close the project and reopen do all three terms exist in the EA glossary window
– and ii) if so do they all output OK with eaDocX

Thanks
Adrian

eaDocX tech support

[Adrian Support]

Many thanks for your feedback.

We have taken note of your request and will look into what is involved within supporting this feature.

Regards

Adrian
eaDocX support team

[Author]

Posts