You need to allow the connection string to be set on the users end. The connection string that you have created has Application scope and is strongly typed. The reason for this is really quite simple. This is when the fun starts as your end users start to say that they can't make a connection to the database on their server. Once you are happy with the application you package and distribute it to your end users. You store the database connection string in the settings of your project. Typically, you first create your database, and then create a connection string in Visual Studio to link to your database, and then you complete the rest of your project. You create a project in Visual Studio which utilizes a backend database. Provided with this post is source code for the connection form which accesses all SQL servers and databases on a computer and its networks, builds a connection string based upon user selection, and also saves this to an xml file in local data storage (see bottom of post for download). The approach used allows end-users to change database connections at runtime through a friendly user interface, and save the connection for future uses. Is there a better way to do all of this, or am I on the right track? I would appreciate any assistance.This blog post details a solution to the common problem of dynamically setting connection strings. I just want to build out a package that will allow me to pull data from the MySQL and push to a SQL server. The problem is that I cannot find a 圆4 driver for MySQL for VS.
I looked up the error, and it appears that there is a mismatch between the x86 and 圆4 drivers. However, now when I try to connect, I get "ERROR The specified DSN contains an architecture mismatch between the Driver and Application". It seemed to work, and I was able to see the connector in VS. I still could not get the MySQL connector to appear when I tried to connect a new database to VS, though.įrustrated, I decided to create a User DSN (as opposed to a System DSN) and connect that way. So then I installed the connector by itself, BEFORE installing the ODBC or NET connectors and I got it to install. Each time I would attempt to install the MySQL for Visual Studio connector, the installer would say that Visual Studio was not installed on my computer.
NET connectors, and I tried reinstalling them over and over again. So I uninstalled Visual Studio, the MySQL ODBC and.
My first problems began because the MySQL installer would not recognize the installation of Visual Studio (even though I ALSO have 2013 installed!). I have followed the instructions listed on the MySQL website - I have tried the MySQL Installer as well as the standalone download. I just want to be able to add a MySQL database as a database connection in VS so I can build an integration. For the life of me, I cannot get the MySQL for Visual Force connector to work in VS.
0 kommentar(er)
