|
>> I think we approach the concept of procedures a little differently. No I think we just completely mis-understood one another. I had assumed (incorrectly obviously) that being the little old tool builder that you are you'd have written a tool to build your protos for you. Then as they were adapted to procs would modify them appropriately. As to "result sets" - l simply meant the pieces of data returned by the proc. The point I was trying to make, which seems to have been missed completely, was that protos have nothing to do with procedures per se - a program call can be prototyped, as can a bound call to a "program" module, as can a function or procedure. I just happen to think that adding this level of bullet proofing to the call is _always_ worth while. Jon Paris Partner400
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.