Re: [WebERP-developers] Other feature to develop

[Phil D. <ph...@lo...>]

Makes sense in principle. Can you explain a bit more how vendors would move between these statuses and where we might use these other statuses or is this for integration with an external quality system or just report in?
-- 
Phil Daintree
+64(0)275 567890
Skype: daintree

On April 26, 2014 3:04:27 AM NZST, rfthomas <rf...@as...> wrote:
>Phil and Exson,
>
>The system currently allows for having multiple vendors for an item.  A
>vendor may have a status of preferred for an item.  This information is
>kept
>in the PurchData table in the preferred field.  0 = normal, 1 =
>preferred
>
>Why not create a table with choices for this field as is done for UOM,
>etc.? 
>1 retaining it's value, but other values being allowed as defined in
>the
>purchase status table, e.g. 0 - normal, 1 - preferred, 2 - unaproved,
>...
>
>Would such be an acceptable solution?  This is used in only a few
>scripts.
>
>Bob Thomas
>
>
>
>--
>View this message in context:
>http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657373.html
>Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
>------------------------------------------------------------------------------
>Start Your Social Network Today - Download eXo Platform
>Build your Enterprise Intranet with eXo Platform Software
>Java Based Open Source Intranet - Social, Extensible, Cloud Ready
>Get Started Now And Turn Your Intranet Into A Collaboration Platform
>http://p.sf.net/sfu/ExoPlatform
>_______________________________________________
>Web-erp-developers mailing list
>Web...@li...
>https://lists.sourceforge.net/lists/listinfo/web-erp-developers