Field widths shouldn't make any difference, you do you varchar(50) or nvarchar(50) or (100) already don't you for the data outside of State?
In all of my code the UI data is defined by the received data from the backend.
On Fri, Mar 11, 2016 at 4:13 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2016-03-10 17:53, Stephen Russell wrote:
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)
Oh hell no. I see that as torture and ripe for problems. What happens if I go and change the field widths? Then I have to visit every instance/reference and update. NO THANKS.
[excessive quoting removed by server]