MySQL And VB

Hi, I have the MySQL ODBC Driver for connecting to a MySQL Database in Visual Basic. I will be having about 30 individual databases which normally would mean manually setting up 30 ODBC Connections on each of our 50-60 pc's. Is there an easier way of doing this? Since all my connection strings are coded in the programs as follows:

VB Code:

cn.ConnectionString = "Provider=MSDASQL.1;Persist Security Info=False;Extended Properties=DATABASE=DataBase_Name;DESCRIPTION=MySQL NCMR Database;DSN=DSN_NAME;OPTION=àà z;PORT=0;SERVER=192.168.50.4;UID=brandone"

Is it possibly to just have one ODBC DSN on each PC that could handle all 30 programs?

The option is to create db connections within the code:

Connection to local MySQL database using MySQL ODBC 3.51 Driver

"Provider=MSDASQL; DRIVER={MySQL ODBC 3.51 Driver}; SERVER=localhost; DATABASE=Your_MySQL_Database; UID = Your_Username; PASSWORD=Your_Password; OPTION=3"
(Ref:http://www.sqlstrings.com/MySQL-connection-strings.htm)

In such a case you do not need to configure the dsn on each PC.

Take a look at this link

I see now, Thank you!. So DSNs are mostly for people that use the ADODC/DAO Controls instead of ADO coding in vb?

DSN's were the original method used to work with ODBC, but DSN-less connections have since been enabled. DSN's have effectively been depreciated, as they are an unnescessary part of the setup process.

You can still use DSN's if you like, but DSN-less connections are much more flexible, especially if your program can connect to multiple databases.

I haven't tried it, but I'd expect that data controls allow DSN-less connections too.

Quote:

---

Originally Posted by LostAngel

I see now, Thank you!. So DSNs are mostly for people that use the ADODC/DAO Controls instead of ADO coding in vb?

---

Read this: Why Data Binding and the like are evil

Quote:

---

Originally Posted by Mark Gambo

Read this: Why Data Binding and the like are evil

---

Thanks, i've read that many times and have that hanging on my office wall lol. I always use hard coding instead of the ADODBC Control, but have always used DSNs for some reason. I think pretty much the first 'connectionstring' I saw, had a DSN in it and I always kept that format..but thanks to pranoy, I have one that is GREAT.

Quote:

---

Originally Posted by LostAngel

Thanks, i've read that many times and have that hanging on my office wall lol. I always use hard coding instead of the ADODBC Control, but have always used DSNs for some reason. I think pretty much the first 'connectionstring' I saw, had a DSN in it and I always kept that format..but thanks to pranoy, I have one that is GREAT.

---

Also take a look at www.connectionstrings.com