Mackin, Christopher
CMackin at Quiznos.com
Fri May 7 13:22:45 CDT 2004
The 7 lines gives you more information, that's why it's preferable in my mind. Specifically I like to see exactly what the Parameter names are, their data type, the Input/Output designation and the value being passed to it. For a 1 parameter stored procedure it is not very useful, but when you start getting more and more parameters in there it keeps things much cleaner. I also don't want my code to be dependent on matching the same order the parameters are listed in the Stored Procedure and in my call to it. One less thing to worry about. I am unaware of any performance benefits of one over the other and advocate the "longer" method purely out of readability and personal preferences. It's the same reason that I write: Dim strSample as String instead of the short version: Dim strSample$ -Chris Mackin -----Original Message----- From: Brett Barabash [mailto:BBarabash at tappeconstruction.com] Sent: Friday, May 07, 2004 11:34 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Executing Stored Procedures in a A2K ADP? Hmm... This really is the first time I've heard multiple people saying that 7 lines of code were easier to read than 1. Does ANYONE use the method syntax for executing stored procedures? I realize it's a newer ADO feature but I've found it to be extremely useful in reducing the volume of ADO code in my projects. -----Original Message----- From: Mackin, Christopher [mailto:CMackin at quiznos.com] Sent: Friday, May 07, 2004 10:13 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Executing Stored Procedures in a A2K ADP? Also it doesn't rely on entering the parameters in any specific order. I mainly prefer that method for the same reason Gustav pointed out, it's much easier to read thus easier to debug when you have to or when you come back to the code a year down the road. -Chris Mackin -----Original Message----- From: Gustav Brock [mailto:gustav at cactus.dk] Sent: Friday, May 07, 2004 8:59 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Executing Stored Procedures in a A2K ADP? Hi Joe Yours is easier to read. /gustav > Does anyone have an argument for not using this method as oppose to my > example below? -- ---------------------------------------------------------------------------- ---------------------------------------- The information in this email may contain confidential information that is legally privileged. The information is only for the use of the intended recipient(s) named above. If you are not the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or the taking of any action in regard to the content of this email is strictly prohibited. If transmission is incorrect, unclear, or incomplete, please notify the sender immediately. The authorized recipient(s) of this information is/are prohibited from disclosing this information to any other party and is/are required to destroy the information after its stated need has been fulfilled. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Tappe Construction Co. This footer also confirms that this email message has been scanned for the presence of computer viruses.Scanning of this message and addition of this footer is performed by SurfControl E-mail Filter software in conjunction with virus detection software. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com