bob

[bob]

Hi Ian

I have had a go at defining this and suggesting a way to do it for comment.

Bob

[bob]

Hi

Just hit my first issue.

Glossary section inserts table brakes by Term Type.

Also as it did in V3, the table footnote is mall-formed. It remains as $Table$ rather than being replaced by a table number and text.

Bob

[bob]

Thanks.

In what sort of time frame will V4 be available?

[bob]

Thanks for the information.

I have been experimenting and managed to identify the issue.

The location the document is in and the .eap file is on One-drive. If I create a document on my C: drive it all works as expected.

Looks like having One-drive locations doesn’t allow this temp.rtf document creation as I don’t see it flashing up when I generate. I do see it flash up on my local drive.

This is an issue as my company have made all my document locations One-Drive synchronized for backup purposes.

Any idea if there is some setting that will allow this behavior on OneDrive areas?

Bob

[bob]

Completed the suggested steps as above.
All works great now.

Thanks for the help.
Bob

[bob]

Any comments on this?

[bob]

I upgraded:-
from Windows 7 to Windows 10
from Office 2013 to Office 2016 (although it claims to be Microsoft Office 365 Pro-Plus)
and upgraded EaDOCX to 3.9.5.7 from 3.7.3.0.

Now it doesn’t work and I can’t eve open any document I created in it within EADocX.
Outside they open fine.

Bob

[bob]

I am running 3.9.5.7.
I re-downloaded anyway and repaired my installation.

No change still get the same error.

Bob

[bob]

Hi
I repaired Office but no change. I did a search for the dll and it is not present.
I noticed that Windows claims my Office Version is Microsoft Office 365 Pro Plus but the program is Word 2016. Does this have any bearing on the issue?

Bob
P.S. Why does the EADocX Installation Validation say both the low level and high level interfaces are OK and open a word doc but the real program cannot?

[bob]

Hi I got the same message as this guy gets when I tried to generate any documents. Regardless of weather they were newly created or old documents.

A bit of reserch later and it appears that the updated calls you refer to didnt arrive untill build 2012. Latest update is 2015 so I upgraded and now all is well.

Thanks for the prompt reply anyway.

[bob]

I am using EA build 12.10 and eaDocX 3.6.2.7 and I get the same issue.
I cant generate any documents.

[Author]

Posts