Drew Wutka
DWUTKA at marlow.com
Wed Jul 16 11:01:02 CDT 2003
I agree too, I was just saying it wouldn't matter much either way. Ideally you want to connect and release, but the issues going either way are pretty level. I have run into situations where keeping a persistant connection is an absolute must, and I have had the opposite too. This situation didn't seem to really matter either way, but you're right, the preferred method would be to release what you are not using. Drew -----Original Message----- From: Bobby Heid [mailto:bheid at appdevgrp.com] Sent: Wednesday, July 16, 2003 8:47 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] ADO question: VB FE to SS7 >From a program point of view, I agree that it does not matter. But good programming practices say that you should release your connection to the server as soon as possible. And since you have a pretty low connection rate, I would have to say that I think that you should recreate the object each time you need it. The speed penalty to your program should be imperceptible. This allows the most efficient use of your SQL server. Just my $0.02. Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Drew Wutka Sent: Tuesday, July 15, 2003 4:40 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] ADO question: VB FE to SS7 I don't think it is really going to matter. If you don't want to leave the object loaded, then create and close it each time. That makes the process take a wee bit longer. If you want to leave it open, then do so, that just keeps a live connection to the database. Either way, both 'effects' are minimal, so I wouldn't be concerned either way. I say this because you mention 200 to 400 a day. That's a lot less then 1 a minute. I wouldn't be concerned about opening and closing it unless you were talking aobut 20 to 30 a minute (one every 2 or 3 seconds....), because then the open and close method would be taking up more valuable time, and you might end up with periods of backlog. Drew -----Original Message----- From: Joe Rojas [mailto:JRojas at tnco-inc.com] Sent: Tuesday, July 15, 2003 2:46 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] ADO question: VB FE to SS7 Hi All, I am working on a VB app that will be used to store telephone call information to SQL Server 7. The VB app is monitoring the serial port for incoming data. Once a complete call record is received that record will be parsed and then added to the database. My question is, should I create a static ADODB command object and used it over and over as needed or should I destroy and recreate the ADODB command object each time it is needed? What are the pros and cons? On average, the number of records being added per day, during working hours, would be around 200 to 400. I want this application to be running 24/7. Any suggestions? Thanks, Joe R. This electronic transmission is strictly confidential to TNCO, Inc. and intended solely for the addressee. It may contain information which is covered by legal, professional, or other privileges. If you are not the intended addressee, or someone authorized by the intended addressee to receive transmissions on behalf of the addressee, you must not retain, disclose in any form, copy, or take any action in reliance on this transmission. If you have received this transmission in error, please notify the sender as soon as possible and destroy this message. While TNCO, Inc. uses virus protection, the recipient should check this email and any attachments for the presence of viruses. TNCO, Inc. accepts no liability for any damage caused by any virus transmitted by this email. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com