If you happen not to know OpenERP, its one of the best opensource ERP solutions. There is also OpenBravo, but why I settled to concentrate on deploying OpenERP is because its simpler and quicker to fix errors as compared to OpenBravo.
I have installed the 5.0.6 version on a number of clients and overtime we have had to fix some bugs the mad scientist way.
What I mean by mad scientist way, we don’t document changes, we don’t use any version control, and we leave the fixes at the client. But this hasn’t gone really well over time, as the number of bugs in accounting and currency issues have increasingly crippled up as its being used more. Read more…
Last week I was faced with the dilemma of increasing the price accuracy from 2 to 3 in OpenERP for a client who uses OpenERP server 5.0.6
OpenERP server has a configuration for the price accuracy in its configuration file, but as of 5.0.6 it seems to be to effective.
Changing the value in the config from 2 to 3 had no effect. On Googling around it seems to be a bug that may be fixed in the upcoming 6.0.0 release.
However the price accuracy config option can be passed directly when starting the server. This option works for both Linux and Windows. However windows has a major draw back that the windows service that creates the openerp-server process does not allow passing additional parameters. Though u can start the openerp server manually in windows with the parameter, when it comes to having the server started by the service, it won’t work. Thus the need to have to pull source code of the openerp service from launchpad, modify it to pass price accuracy parameter, and recompile it. Read more…