I never use DAO. Is there any benefit over ADO?
Thanks Emery ----- Original Message ----- From: "Roger Davis" <[EMAIL PROTECTED]> To: "Director General: NEFACOMP" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 18:14 Subject: RE: Ideas on creating connections > My experience is this. I use DAO through MyODBC, and I also use the > libmysql.dll with a custom recordset. Connection times through both options > are extremely fast. Fast enough in my situation that it can basically can be > ignored. There are times when I open several connections to the server at > once and have yet to run into any problems. If you strictly want to use ADO > though, I would suggest that you open one connection to the server and > process your queries through that connection. Leave it open for the life of > the program. While the program is open, the connection to the server will > stay open and the thread for MySQL will be a "sleep". > > Just my $0.02. > > Roger > > -----Original Message----- > > From: Director General: NEFACOMP [mailto:[EMAIL PROTECTED] > > Sent: Thursday, September 25, 2003 11:57 AM > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Ideas on creating connections > > > > > > Hi groups, > > > > I need some experienced users to guide me on this issue. > > I am developping an Application that will be accessing a MySQL > > database through MyODBC. > > The application is developped using Visual Basic. > > > > Since my application will be used simultaneously by more than 200 > > users, I want to know the implication of using one of the > > following methods for connecting to the server: > > > > 1. At logon, I create a connection to the server and maintain it > > throught the application life. By the application life I mean > > that the connection stays open as long as the application is > > loaded in the memory. So, for a user who is online for 3 hours, > > the connection is on for those three hours, even if the user goes > > out for a coffee. > > > > 2. I create a connection only when a query is about to be sent to > > the server. That means, I create a connection when I want to > > create an ADO recordset and run a query against the server. After > > running my query, I distroy the connection. > > > > > > Currently I am using the first option since I don't exactly what > > it is required (time and resources) to make a connection to the > > server. Will you please tell me how fast is to connect to the > > server. If you advise me that this method is the best, I will add > > functions to reconnect a dead connection. > > > > > > Any ideas and advices are highly welcomed > > > > > > Thanks, > > __________________________________ > > NZEYIMANA Emery Fabrice > > NEFA Computing Services, Inc. > > P.O. Box 5078 Kigali > > Office Phone: +250-51 11 06 > > Office Fax: +250-50 15 19 > > Mobile: +250-08517768 > > Email: [EMAIL PROTECTED] > > http://www.nefacomp.net/ > > > > --- > > Incoming mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.520 / Virus Database: 318 - Release Date: 9/18/2003 > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.520 / Virus Database: 318 - Release Date: 9/18/2003 > > > -- > MySQL ODBC Mailing List > For list archives: http://lists.mysql.com/myodbc > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
