EA 16 and .eapx files

[Martin Merkel]

Hi, this week I installed EA 16 (1604) on my Windows 10 systems. On one of them I can neither open, nor create .eapx files. I get an error>:  ADODB.Connection error : 800A0E7A
Files are all local on the disk, not on a server. What is missing here?
Thanks, Martin

Ps: I can open the files with the earlier 15.2 installation

[wivel]

Hi Martin

Keep in mind, that .eap(x) files are only supported in the 32bit version of EA 16, not the 64bit version.

You can read more here: https://www.sparxsystems.com/products/ea/16.0/index.html#A1A63754-7544-4d8f-96BF-AD83B263439F

Henrik

[Martin Merkel]

Hi Henrik,
thanks for the hint. If have to recheck, but I think on one on my Win 10 systems, I still could open an older .eapx file with the 64 bit version. On this system, I have however at 64 MS Office installation, whereas one my notebook, there's only a 32 bit version.
Thanks, Martin

[Martin Merkel]

OK, with the 32 bit installation I can at least open the .eapx files. Will verify next weekend on my desktop, where I thought I could open them also with the 64 bit version.
Thanks, Martin

[wivel]

Perhaps you should consider converting your .eapx files to the new SQLITE format. Think it’s called QEAX files now. As I understand both the 32 and 64 versions of EA supports it.

Unless, of course, if you have to exchange models from EA 15.2 and older.

Henrik

[Takeshi K]

Hello all,

If a machine has the 64-bit version MS Office or the MS Access 2010 runtime, and the edition of EA is not Professional, EA can open EAPX files by using the Acess driver.
(at least with build 1603, I have not checked yet with 1604.)

HTH,

[Martin Merkel]

Thanks for all the hints. Given that I have a 32 bit Office package installed, I cannot add the 64 bit Access runtime. So I have to live with the 32 bit version of EA 16 for now on the particular system.
Martin

[ducatiross]

Thanks for posting this question and the answers. I was having the same problems myself, and following the advice in the linked page to create a new QEAX file, then do the project transfer, worked a treat. Thanks for the support