I want the MySQL 5.7.21 server to be installed from my application
-
I want the MySQL 5.7.21 server to be installed from my application why the user downloaded it from the net. My application is ris.msi programmed in VS2015 with c #. The application is installed on the user's machine by clicking on ris.msi without any problems. During the installation of ris.msi I want to install MySQL Server 5.7.21 on the user machine. When I install ris.msi on my machine, everything works ok, but when ris.exe runs on the user's machine, the application cannot connect to the MySQL server. On my machine this works without problems, ris.msi is installed, I run ris.exe and I work with all the tables in the MySQL server, just like I do in VS2015.
-
I want the MySQL 5.7.21 server to be installed from my application why the user downloaded it from the net. My application is ris.msi programmed in VS2015 with c #. The application is installed on the user's machine by clicking on ris.msi without any problems. During the installation of ris.msi I want to install MySQL Server 5.7.21 on the user machine. When I install ris.msi on my machine, everything works ok, but when ris.exe runs on the user's machine, the application cannot connect to the MySQL server. On my machine this works without problems, ris.msi is installed, I run ris.exe and I work with all the tables in the MySQL server, just like I do in VS2015.
Don't. If you want a single user Db, use a single user DB: Access, SQLite, ... If you want a multiuser DB, use a server based system: SQL Server or MySql But don't install a multiuser DB unless you are going to have multiple users using it simultaneously. There are a couple of reasons: 1) They may already have SQL Server / MySql installed on the network. If so, then they will presumably want to use that version. 2) If they do have a server installed and you start proliferating instances, you are going to annoy the heck out of the database administrator... 3) A single site installation of a server DB system is a lot more likely to be backed up than a number of scattered version under user control. 4) Server DB's are quite complex for a "normal" user to install and administer - it is not a good idea! 5) It will destroy the primary advantage of using a Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Don't. If you want a single user Db, use a single user DB: Access, SQLite, ... If you want a multiuser DB, use a server based system: SQL Server or MySql But don't install a multiuser DB unless you are going to have multiple users using it simultaneously. There are a couple of reasons: 1) They may already have SQL Server / MySql installed on the network. If so, then they will presumably want to use that version. 2) If they do have a server installed and you start proliferating instances, you are going to annoy the heck out of the database administrator... 3) A single site installation of a server DB system is a lot more likely to be backed up than a number of scattered version under user control. 4) Server DB's are quite complex for a "normal" user to install and administer - it is not a good idea! 5) It will destroy the primary advantage of using a Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
Ok, there doesn’t have to be more bases. This is a RIS.exe demo program that is located on only one computer, so it is necessary to install the MySQL database only on the computer where the program is. So the user can try out my program, which requires a MySQL database. It needs to be installed and then uses mysqld.exe. I am using MYSQL 5.7.21.0 and I developed the program in MS Visual Studio 2015. Thanks for the help.
-
Ok, there doesn’t have to be more bases. This is a RIS.exe demo program that is located on only one computer, so it is necessary to install the MySQL database only on the computer where the program is. So the user can try out my program, which requires a MySQL database. It needs to be installed and then uses mysqld.exe. I am using MYSQL 5.7.21.0 and I developed the program in MS Visual Studio 2015. Thanks for the help.
I've set my own computer up with Apache/PHP/MySQL several times, and it has always required some manual configuring before everything was just right. I did that to learn, but there are several WAMP packages that install with everything configured automatically. If you don't know, WAMP is Apache, MySQL, and PHP in a package for Windows, thus WAMP. Consider getting one of those packages and including it separately with your demo, and just instruct the clients to first install the WAMP and then install your demo. As you move forward, consider adding more flexibility to your application so it doesn't have to have specifically a local MySQL database. Even if you stay with MySQL, the database should be able to be located anywhere, and all that needs to change is the connection string. Good luck! :)
