I made changes in product.normal.form basically removed fields which we do not
use.
Making changes to product.py requires a restart with --update all . Now all the
changes in the view are gone, product.normal.form is back to the original stage.
How can I prevent this? Maybe I have to save a
Hi,
We're evaluating TinyERP for use in the voluntary sector in the UK. What seems
to be missing in the documentation to me is an introductory guide for setting
it up with a business. The install was easy under Debian, and it even coped
with our Vserver.
What I think is needed is the
I solved this problem (re)writing __init__.py file.
import pos
import sale
import purchase
import account
import account_tax_include
import wizard
import report
NOTE to tiny staff:
Please publish sources of pos module.
Thanks
Simone
___
On 07/09/07 09:33 +0200, [EMAIL PROTECTED] wrote:
+1 ! so, need i think it is not possible in TinyERP ?
damn it ! Access2.0 could do it ! :?
Not yet.
It can be done depending on the state of the object.
If it is a workflow button, you can create role to control the access to
this button.
Hello,
I have an error when trying to create a DB :
1) the client launchs a popup window : Error during database creation !
The server crashed during installation. We suggest you to drop this
database.
2) the server's log contains :
[...]
Fri, 07 Sep 2007 19:03:35
[EMAIL PROTECTED] schrieb:
Making changes to product.py requires a restart with --update all . Now
all the changes in the view are gone, product.normal.form is
back to the original stage.
How can I prevent this? Maybe I have to save a external copy of the view?
Define your own form, eg.
On 07/09/07 09:17 +0200, [EMAIL PROTECTED] wrote:
I made changes in product.normal.form basically removed fields which we do
not use.
Making changes to product.py requires a restart with --update all . Now all
the changes in the view are gone, product.normal.form is back to the original
Richard
Deploying any ERP system is lots of hard work. Understanding TinyERP
is surprisingly easy compared to getting everyone on board for a huge
change. I have worked with small and large companies. As the report
editor gets polished off there will be little to no hangups in
deploying
Yumi wrote:
How can I prevent this? Maybe I have to save a external copy of the view?
I usually make a modified form in a new module using the
field name=inherit_id ref=base.view_XYZ_form / construction. Then you can
update all you like and lose none of your changes -
Yep, I opened a bug on this but Cedric closed it with a comment. Apparently
4.2.0-rc2 is somewhat crippled and I hope the missing pieces will be there in
4.2.0-rc3.
http://tinyforge.org/tracker/index.php?func=detailaid=63group_id=13atid=129
Gerry
I tried and followed your instructions...
netstat -apt showed postmaster listining port 5432.
I changed the user as postres too.
But all failed...
(I also installed openbravo using postgresql that runs well on same machine. )
(I also installed tinyerp to windows that runs well too on the other
Thank for the suggestion. Knerz is of the same opinion. But for me this is far
to difficult. I do not even understand the concept.
As I change only a handful of views, I will keep a copy in a text file and
renew after each --update=all. For now this is a quick and affordable way.
When the
Any news on the Canadian Payroll Module, I'm considering proposing ERP at my
office (in Quebec, Canada) and having payroll is one of the key elements we are
looking for.
Thanks
___
Tinyerp-users mailing list
On Saturday 08 September 2007 08:42:10 [EMAIL PROTECTED] wrote:
Any news on the Canadian Payroll Module, I'm considering proposing ERP at
my office (in Quebec, Canada) and having payroll is one of the key elements
we are looking for.
Thanks
14 matches
Mail list logo
