Yes you do that all the time with sprocs. No biggie adding another one at the end. This is the list of params for an insert.
ALTER PROCEDURE [dbo].[InvoiceLines_ins]
@InvoiceLineID numeric(18,0), @InvoiceID numeric (18,0), @PositionNumber varchar (50), @SequenceNumber varchar (50), @CustomerOrderPosition varchar (50), @CustomerOrderSequence varchar (50), @CustomerBaseUnitCode varchar (50), @CustomerItem varchar (50), @Qualifier1 varchar (50), @Item varchar (50), @ItemDescription varchar (50), @ShipToBusinessPartner varchar (50), @Qualifier2 varchar (50), @ShipToBusinessPartnerCodeinMessage varchar (50), @OrderedQnty varchar (50), @DeliveredQnty varchar (50), @AmountinInvoiceCurrency varchar (50), @Shipment varchar (50), @OrderDiscount varchar (50), @LineDiscountAmount varchar (50), @TaxExemptionReasonCode varchar (50), @TaxExemptionCertificate varchar (50), @DeliveryDate varchar (50), @PriceUnit varchar (50), @QuantityUnit varchar (50), @Price varchar (50)
On Thu, Mar 10, 2016 at 4:50 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2016-03-10 17:22, Stephen Russell wrote:
You will always have to change the UI. How many different places are you asking for the same data? If that was in a Sproc it is fixed all over the place now. If you have it as a statement you pas back you have to go to every occurrence in your app and make the change.
Reporting as well a UI.
Most of us will make the sproc to pull the data for a specific report.
Sure, reporting is fine...use stored procs and you never need to change the UI caller; but I thought you were talking about passing each field as parms to a stored proc.
[excessive quoting removed by server]