From: isgdre@HotMail.com   
      
   In a way I agree with --CELKO--.  The only thing is that it takes money.   
      
   Money for bigger computers to get the job done.   
   Money to deal with the extra complexity of the input screen and the   
   database read/write translations.   
   Money to re-train the development/support staff to the bigger more   
   complex schema.   
   Money to maintain the bigger complex structure for when the business   
   changes and you have it tightly linked like that you will have to   
   re-engineer it or your schema will get out of date and just as bad as   
   using line numbers.   
   Money to pay for the end users extra time in running the application.   
      
   So, I do think if you just take the Money out of the equation then   
   --CELKO-- has a point.   
      
      
      
      
   Ed Murphy wrote:   
   > --CELKO-- wrote:   
   >   
   >>  The order form software should consolidate the lines from the   
   >> PHYSICAL  order form screen or input order form into a row for   
   >> insertion into the tables.   
   >   
   > To reiterate:  in my (and possibly the OP's) particular use case,   
   > retaining the physical ordering of lines is an absolute business   
   > requirement (the client's customers demand it, and we can't demand   
   > they change their relevant processes).  In other contexts (e.g. all   
   > your orders go through EDI), it may well be reasonable to discard   
   > physical ordering in this fashion.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)