kevind
Active Member
   

I was more than willing to "pony up", how b'out U?
Posts: 634
Gender:
|
One of the nice things about views is they enable you to put all of your select criteria into the database instead of the application. If a table definition changes that may affect your select logic, you just re-define the view instead of modifying the application. Your application would just have a simple select all type statement (i.e. select * from <viewname>) I use a view that defines all of the orders that are ready for shipment. The Special part of the view is a nested IF statement that extracts an email address from one of 4 different locations in the sales order. It first checks the sales order notes, then the Description, then the 5th contact in the BKARCUST, and finally the 1st contact in BKARCUST. With an email address, our shipping system (CPS) can email a 'ShipElert' that notifies the customer that a shipment to them has been processed. This email contains the Shipping info and a tracking number.
|