Re: [WebERP-developers] POS

[Tim S. <ti...@we...>]

Hi Jan,

One of the problems with updating the weberp database directly from
the pos, rather than using the api, is that often transactions are
complex and must update several tables, and perform other checks on
the data. Also the db structure can change over time, causing problems
when you do the updates. The api takes care of that and does all the
transactions and checks seamlessly for you.

Tim


On 5 April 2010 08:40, Janvl <jv...@st...> wrote:
>
> Hi Phil,
>
> did you ever actually work with Openbravo POS?
>
> Using Mysql, I only have one Database on the server (intranet) and 3
> POS-locations.
> Stock maintenance is poor, negative stock is possible.
> Discounts can be given on every product, even with a percentage that can
> vary.
> Sales can be done without a product, you only must (can) give a description.
>
> The POS is designed to catch all cash-movements, so you cannot project the
> high
> data-integrety of webERP on the POS if it is openbravo.
>
> This is why I think we should start with transactions that are easily
> feasable, happen on the server and limit it to pooring the data from
> openbravoPOS to webERP because stockmaintenance in webERP is superior to
> that in openbravoPOS.
>
> Kind regards,
> Jan
> --
> View this message in context: http://n4.nabble.com/POS-tp1549501p1751385.html
> Sent from the web-erp-developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>



-- 
WebERP Africa Ltd
+447710427049
+255784602561
www.weberpafrica.com