Voting System using VB.Net and MySQL with Source Code

The Voting System using VB.Net and mySQL with source code is intended for the PHINMA-University of Iloilo Student Council National and Local Elections.

This voting system source code allows the student to vote automated without the use of paperwork.

Also, the Voting System source code using VB.Net automatically tallies the votes of the students as well as gives a statistical program to identify how many students have voted in their respective departments.

The Voting System source code using VB.Net was developed using Microsoft Visual Studio 2013, SAP Crystal Report for the reporting, and the database application used was XAMPP(MySQL).

Voting System using VB.Net and MySQL Features

The Voting System source code using VB.Net and mySQL consists of four categories, the Activation form, the Voting form, the Statistics form, and the Administration form.

Please be reminded that each system has only one database.

Activation Form Features:

1. Retrieves student’s activation column if it is activated or not.

Voting Form Features:

1. Gets the student’s details and verifies if the student has activated his account and redirects to which department the student belongs.
2. An interface where the student can vote for the National and Local candidates. (Local candidates are running from their respective departments).
3. Easy confirmation process.
4. Vote-once mechanism, the student cannot vote anymore after casting his/her votes.

Administration Form Features:

1. Shows the student’s details (e.g. if voted or if activated)
2. Shows the accumulated votes by each candidate (National and Local)
3. Shows the student’s voted archive (for double checking or if a student complains)
4. Shows administrator’s logged-in and out details

Statistics Form Features:

1. Shows the percentage of votes and not in each department.
2. Shows the overall percentage of voted and those who did not.
3. Real-time update of statistics.

Download the Source Code

Click the button below to download:

Database Name:

phinmaui_elections.sql

RAR Extraction Password:

Password: luffypirates

Related topic(s) that you may like:

• Creating mySQL Connection using VB.Net
• Event Tallying with Voting System Using PHP and mySQL database

For questions or any other concerns, you can leave a comment below.

Technology stack and requirements

To run this VB.NET project, you need the following on your development machine:

• Visual Studio 2019 or later. The free Community Edition is enough for building, debugging, and running the project.
• .NET Framework 4.7.2 or higher. Most Windows 10 and 11 systems have it preinstalled through Windows Update.
• MySQL Server 8.0 or MSSQL Express 2019. Choose whichever your capstone panel prefers; both work with VB.NET data adapters.
• MySQL Connector/NET or SqlClient library. Add via NuGet Package Manager inside Visual Studio.
• Crystal Reports (optional). Required only if the project generates printable reports; install the runtime redistributable.

Installing the source code

The download link contains a ZIP archive with the full solution. Extract and set up in five steps:

1. Extract the archive to a folder outside Program Files (avoids permission issues).
2. Open the .sln file in Visual Studio. It loads the full solution with all forms and modules.
3. Restore NuGet packages. Right-click the solution then Restore NuGet Packages if prompted.
4. Import the database. Locate the .sql file in the archive and import via phpMyAdmin (MySQL) or SQL Server Management Studio.
5. Update the connection string in App.config or module code to match your local database name, user, and password.

How to use this project for your BSIT capstone

This VB.NET project maps cleanly to standard BSIT capstone documentation. Suggested chapter alignment:

• Chapter 1 (Introduction). Discuss the problem the system solves in real-world context. Cite Philippine business or academic use cases where a manual process could be replaced.
• Chapter 2 (Review of Related Literature). Compare this system’s features against 5-10 similar published projects. Cite journals like IJERT or IEEE Access for academic-standard sources.
• Chapter 3 (Methodology). Include Use Case Diagram, Data Flow Diagram, Entity Relationship Diagram, and Activity Diagram covering all major workflows in the system.
• Chapter 4 (Results and Discussion). Screenshot each module of the running system with a caption explaining what data it processes and which user role interacts with it.
• Chapter 5 (Conclusion and Recommendations). Identify features that could be added in a Version 2, such as web dashboard, mobile app, or REST API export.

Modules typical of Voting System using VB.Net and MySQL

• Master data. CRUD forms for the primary entities the system manages, with search and filter.
• Transaction processing. Data entry forms for the day-to-day operations the system automates.
• Reports. Formatted printable output summarizing activity per day, per user, or per category.
• User management. Login with role-based permissions (Admin, Encoder, Viewer).
• Backup and restore. Export database to a .sql or .bak file and restore when needed.

Common enhancements for capstone review

• Modernize the UI. Add Bunifu or Guna UI controls for a more polished, modern appearance.
• Add printable receipts. Integrate a printer preview form with page-setup options.
• Multi-user concurrency. Ensure the database handles simultaneous writes without lost-update errors.
• Web version. Rewrite the front-end in ASP.NET Core or React for a modern deployment path.

Project timeline estimate for BSIT capstone

Typical BSIT capstone teams complete a VB.NET project of this scope in one full academic semester. Suggested timeline:

• Weeks 1-2. Requirements gathering, interview with the target user or institution, and initial documentation of Chapter 1.
• Weeks 3-4. Design phase: use case diagram, DFD, ER diagram, and mockup screens on paper or Figma.
• Weeks 5-8. Core development: database schema in MySQL, main forms in Visual Studio, CRUD operations.
• Weeks 9-11. Reports, printing, and user roles. Test with actual sample data from the target institution.
• Weeks 12-13. Documentation: finalize Chapter 3 methodology, Chapter 4 screenshots, and Chapter 5 conclusion.
• Week 14. Mock defense with adviser, corrections, and final panel presentation.

Panel questions this project typically gets

Prepare answers to these questions before your capstone defense — panel members ask them almost every time:

• What existing systems are similar and how is yours different? Prepare a comparison table showing 3-5 alternatives (usually commercial products or older thesis work) and the specific gaps your project addresses.
• How do you validate data entry to prevent bad input? Walk through the validation logic on 2-3 key forms, showing regex checks, range validation, and required-field enforcement.
• How does the system handle concurrent access? Explain your database transaction strategy — SQL locking, timestamps, or optimistic concurrency.
• What is your backup and disaster recovery plan? Have a documented backup schedule (daily, weekly) and a restore-from-backup demo ready.
• How would you deploy this in production? Explain the Windows installer, database setup script, and how updates would be delivered.

Deployment options after the defense

Once you graduate, this system can be extended into a real product with these deployment paths:

• Local Windows install. Package with Visual Studio’s built-in ClickOnce installer for small businesses that only need one computer.
• Multi-terminal LAN. Host MySQL on one server PC and let 3-5 client PCs connect over the office network.
• Cloud migration. Move the database to Azure SQL or AWS RDS and keep the Windows Forms front-end for existing users.
• Web rewrite. Rebuild the front-end in ASP.NET Core or React while keeping the same database and business logic.

Common defense pitfalls to avoid

• Empty database. Always pre-populate 20-50 realistic sample records so demos are meaningful — an empty grid looks unfinished.
• Missing error handling. Panel members love breaking your system. Wrap every database call in Try/Catch and show user-friendly error messages.
• No printable output. Every capstone panel expects at least one printable report. Add a Print Preview form.
• Untested login. Prepare a demo Admin user, a demo Encoder user, and confirm both work before showing the panel.
• No backup demo. Have a scripted database-backup and restore demo ready in case the panel asks.

Where to get help while building

• itsourcecode.com free downloads. Browse other VB.NET projects for similar patterns and code examples.
• Microsoft Learn VB.NET docs. The official reference for language syntax and .NET class libraries.
• Stack Overflow VB.NET tag. Fastest place to get unstuck on a specific error message.
• YouTube capstone walkthroughs. Search for demos of similar systems to see how other students structure their defense.
• Your adviser. Regular check-ins keep the project on track and surface issues early rather than at defense day.