I am having trouble developing and fixing bugs in real time.

So far I have used VS 2005 project to develop my VB.NET application, and another installer project in VS 2005 to create *.exe and *.msi files to install my application on other computers in the domain.

However this is not efficient neither comfortable. I have to interrupt my coworkers to install new version of my application on their computer.

We have NAS disk, where we can put applications and share them across the domain. I want to be able to publish/deploy my application on this shared disk and since Click Once enables auto-update each time the application is started, this way I am able to fix bugs in real time.

However, to make things more nastier, we still use 32bit IBM DB2 database which happens to have problem with 64bit Windows 10. Well I am not 100% sure about this statement.

I tired to publish with Access 2000 mdb file which works like a bridge to our DB2 database, but I am having trouble to use it in my application.

What if I want to open the mdb file with a button and then use the Access 2000 GUI to do stuff on the DB2 tables? Does the Access 2000 proecess gets locked once opened trough a WinForms button?

What is the best way to publish application with a mdb file? Should I include it in "Application Files" in the Publish tab in Project proerties?

Or some other tab should be used to add external files? Extensions or References tabs maybe?