Well is better use Access or MySQL with WIN (JAVA) APPS (desktop), where find cons and pros ?

each has their benefits and each has their drawbacks

Access/JET is a file server type DB, its fine for small applications, its fairly transportable and has modest server needs.
MySQL is a servewr DB that can support significantly bigger volume of data and users.


MySQL will ruin on many different platforms whereas JET is usually Microsoft only. if you want the size and transportability of Access then consider something like Apache/Java Derby.

JET runs with little or no administration required, where as MySQL does need some admin. the security model in both db's is flawed, although the JET security model is seriously flawed, its tough to fully tie down the security of data in a JET database. MySQL is far better, but it still doesn't comprehend the idea of groups and roles (or at least it didn't last time I looked seriously at MySQL security.

MySQL is a scalable db engine that can support many many users, JET doesn't and can't, JET is limted to around 2 GB of data, MySQL dependenat on server and cofig settings can be anywhere from 4gb upwards

didn't you already ask this question before?

Access is for desktop or web Apps BUT MySQL is ONLY for web Apps ?

Aren't you asking yourself the wrong question ?
You should look at the requirements and user environment of your application(s) and from that the choice of DB should follow. If one of the 2 simply cannot do what your application requires then that makes your choice easy.

If both are suitable then it's a matter of listing priorities and making a choice.
It doesn't make sense to choose one or the other on their own, depends what you want to use the DB for.

If you mean which one is best from a Java developer point of view then the answer is the same. The programming required is as easy or difficult for both so you are back to application requirements.

each client then must have installed the mysql server to connect mysql<>desktop app? or... how works?

Yes, if the application uses MyQL then MySQL must also be installed on the computer running your application. The Java application "talks" to the MySQL server in order to update the database used so it needs to be installed as well.

If you want a Java application that uses a database but is not dependend on any other application actually being present on the computer it runs on, then maybe you should consider using an embedded database. Do a google search on "java embedded database" and you'll find multiple examples.

many clients can talk/connect to one MySQL database, even if each cleint is runnign a different application talkign to different back end databases. if the data is owned by the same organsiation you can run one MySQL server (or any other server) to support as many clients as required

however if you see one applciation being used by many different organsiation then you will need torethinkg how the data shoud eb stored. if its one client one coipy of the data then an embedded dtaatabse or Apache/Java Derby may be an appropriate data storage mechanism.

your question is not really somethign that can be given a detailed or accurate answer because you don't provide enough information on what you are trying to do

you say for standalone apps jdk/mysql need to be installed(no network), well is any way make an exe file self integrated/standalone without the need either installed ?

No, for a standalone Java application to use a MySQL database it must talk to a MySQL server which is a seperate application and process. As you talk about a standalone application i'm assuming you want the application to run on a single computer.

It is possible for a standalone Java application to "talk" to a MySQL server which is actually located on a different computer, usually a webserver. And here multiple applications on different computers can "talk" to the same MySQL server, that why it's called a "server" btw. But then you are not really talking about a stand-alone application anymore as you use multiple, ie. at least 2 computers. Maybe your program is stand-alone but your application isnt. Big difference.

If you want the database to be an integral part of the application, self-contained, independent, embedded, whatever you want to call it then it cannot be MySQL but you have to use one of the other options.


Nothing sensible can be said without you actually describing what it is you want your application to do.

if we have no connection and want to build an app personal for one person , no intranet , lets say a hotel booking system data keep, old fasion well in this case how handle ?
Access in this case ? Application will sell in small size 4MB...in exe file...

Yes..........