Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: kepNCI on September 01, 2016, 01:42:25 am
-
Since Access 2013+ no longer supports reading mdb databases, (and I assume MS no longer supports JET 3.5 and 4.0 databases), I was wondering if there are plans for eap files to start using newer versions of the jet engine databases.
I have used Access 2010 to link to eap files so that I can look at the database structure. I cannot do that with Access 2013 and greater.
-
Jet 4 is licensed differently to 3 (which is likely free). That's the simple reason why EA comes with that old version. I guess that will not be changed (I asked that some years ago).
q.
-
The corporate edition of EA supports connecting to accdb files for Access 2007 (and possibly later.)
The other alternative if you want to move away from access files is to use a firebird file.
-
Since Access 2013+ no longer supports reading mdb databases, (and I assume MS no longer supports JET 3.5 and 4.0 databases), I was wondering if there are plans for eap files to start using newer versions of the jet engine databases.
I have used Access 2010 to link to eap files so that I can look at the database structure. I cannot do that with Access 2013 and greater.
Access 2013 will support Jet 4 MDB files (and will even save them). We use it all the time. It's Jet 3 that is not supported. I think we can allow MS to drop support for an (as of 2013) an 18 year old technology.
Paolo
-
You don't need MS access to access (pun intended) your Jet 3 .eap file.
I even find MS Acces an exceptionally bad SQL client.
There are enough free SQL clients you can use and that are much better. I personally use AnySQL Maestro (https://www.sqlmaestro.com/products/anysql/maestro/download/)
Geert
-
I just tested it. Like Access 2013 as Paolo stated, Access 2016 also reads JET 4.0 files. I therefore do not have a problem.
My "REAL" problem was my own error in that I was using a Jet35 eap project that I thought was JET 4. I was testing this at home on my home PC which has Office 2016 and where I forgot to replace the EABase.eap file with the JET 40 version. At work I am still on Access 2010 plus I know I am using the JET 40 base file in EA and thus did not encounter the error.
Geert: Totally agree, but it is hard to teach an old dog like me new tricks. I have used MS Access for many years. I use it mainly as a quick application to create tools that I need. (I am far from being considered a good application programmer.) In this case I have a set of MS Access programs that reads our Network Config's SQL Server database to create MS Access database snapshot of our network. I then have another MS Access program that reads that Access database snapshot and compares it with a huge EA Project on SQL Server in which I replicate our network config. In addition, the corporation tends to frown on using free ware.
All of you...Thanks for the input.
Karl