From: [EMAIL PROTECTED] > To specify, I am using a single ADO command (and connection) object(s) > in a script, and more than one subroutine uses them. Since each stored > procedure has a different number of arguments, I can't leave the > references hanging around. Is there any benefit to creating and > destroying a new ado command object each time (sharing only the > connection object)?
Well creating ADODB.Command is not free. So if you use several stored procedures a lot you'd better create separate ADODB.Command objects and keep them. It'd be quicker. How big difference would that mean depends on your script, but I'd think it could be noticeable. Jenda =========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ========== There is a reason for living. There must be. I've seen it somewhere. It's just that in the mess on my table ... and in my brain I can't find it. --- me _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
