How to publish Visual Studio project with mdf file?

[kutlesh]

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?

[NeedSomeAnswers]

So i have some questions,

Your IBM DB2 Database must be networked surely as it will live on a central box? ie does it live on a central server which everyone connects to?

If so then why on earth would you want to introduce an access database in between?

If for some reason your installing it locally that would be good to know?

If you are having problems connecting to your DB2 database you should fix that directly. If you are using Access as a way to view the tables and manipulate them as DB2 does not have a GUI like SQL Server then surly you only need to do that on your developer machine?

I feel like we are missing information here that is required to help you properly

[kutlesh]

Hmm, gonna test now empty project with DB2.

But I am facing an utter ugliness here... 6 apps, which are like 70 percent the same are built as separate pieces of software, so now I am doing the same thing 6 times...
And I have no help from others...



And guess what, everything is interwoven with the GUI interface of the form, no actual data/application state class/object where all collected data is kept safe...

[topshot]

I'd agree to scrap trying to use Access as an ODBC interface to DB2. Why are you not using the appropriate IBM.Data.DB2 .Net provider in your app?

Since you say you may have an issue with 64-bit Win 10, are you running DB2 on Windows also?

Our's is on an IBM System i server and I am not aware of any issue with Win 10 clients.

[kutlesh]

What you recommend is this: https://www.ibm.com/support/knowledg.../c0010960.html

???

Well back in 1998 Linux wasn't so popular and improved. Yes, I think we have 32bit IBM DB2 on some of those old Windows Server operating systems

[topshot]

What you recommend is this: https://www.ibm.com/support/knowledg.../c0010960.html

Yes. I have been told by IBM support that it is not fully .Net compliant but will still give the best features and performance.

[topshot]

What you recommend is this: https://www.ibm.com/support/knowledg.../c0010960.html

Yes. I have been told by IBM support that it is not fully .Net compliant but will still give the best features and performance.

I'm not sure if that specific one will require IBM Client Access for Windows to be installed or not (in case that is not normally installed on your PCs). It must be if using the iSeries version.