Member Avatar for PoisonedHeart

Hello to All, Good day :)

I have developed a vb6 project with Ms Access as it's database.
When I use Ms Access as a database, during the package and deployment, I will just have to add the file ".mdb" then all is done...
-Ready to install in the client's machine..since Ms Access is file-based db.. if you got the ".mdb" file, then your app is ready to go...

However, I want to change my database into a MySql database..

My problem is, how will I deploy my project and install it on my client's machine without having problems with my mysql database,

If its ok, if someone have a free time would someone provide web links or examples, regarding this topic.

Advanced Thank you to all the readers... :)

  • 2 Contributors
  • 2 Replies
  • 205 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by PoisonedHeart

Dani AI

Generated

Moving from Access (file-based) to MySQL (server-based) changes deployment from “copy the .mdb” to deciding where the database runs and how clients reach it. As suggested, common approaches are: bundle and configure MySQL in your installer, use a third‑party installer (Inno/NSIS/etc.), or provide a separate MySQL setup and clear instructions so the customer chooses the server machine. Each approach affects network, security, and who is responsible for backups and upgrades.

Practical checklist for deployment:

  • Central server: install MySQL once on a server, import schema, create a dedicated non‑root DB user with minimal privileges, open only the required port (default 3306), and restrict access by host/IP. Enable SSL or VPN for Internet access and schedule regular backups (eg. mysqldump).
  • Single‑machine (app + server on same PC): have the installer register MySQL as a Windows service, import the schema at install time, and create the app user interactively rather than shipping root credentials.
  • Hosted/managed DB: avoids local MySQL installs but requires secure connections and IP/credential management.

VB6 connection and driver notes (common source of trouble): VB6 apps typically use ADO over ODBC. Use a DSN‑less connection to avoid having end users create DSNs, and be mindful of 32‑bit vs 64‑bit drivers (VB6 is 32‑bit). Example DSN‑less template (replace driver name as installed):

Provider=MSDASQL;Driver={MySQL ODBC DRIVER NAME};Server=SERVER_IP;Database=DBNAME;Uid=APPUSER;Pwd=APPPASSWORD;Option=3;

Troubleshooting checklist: confirm MySQL service is running, check bind‑address and firewall, verify the correct ODBC driver bitness and DSN admin (%windir%\SysWOW64\odbcad32.exe on 64‑bit Windows), ensure the app connects with a non‑root user and that that user’s host is permitted. For migration from Access (for ), export data to CSV or use a migration tool, verify types/auto‑increments, and test the full install on a clean VM before shipping.

Recommended Answers

All 2 Replies

Member Avatar for vb5prgrmr

You will have to add the setup files to your setup package.

Then you have a couple of options...

1) Customize the Setup1.exe project so that it installs the MySQL files with, if any, of the appropriate command line switches if user wants it on that particular machine. Meaning, install the service on one machine as the server and just the program on other machines. (I must warn you that if you go this route, you need to make at least two backup copies of this project that you can find where vb is installed on your computer)

2) Use Inno, Wise, or some other 3rd party software to do this for you.

3) Include it as a seperate setup package with instructions on how to setup the system, especially if you are wanting to make it easy on yourself and the end user so that they can pick the machine the service is installed on.

Good Luck

Member Avatar for PoisonedHeart

Thank you for your reply.,.,I'll try this at home.,.:)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.