Translations by buke

Part One, :ref:`part1-steps`, starts with the installation of OpenERP. If you have already installed OpenERP you can directly take your first steps on a guided tour in the :ref:`ch-guided` chapter. If you are already familiar with OpenERP or Tiny ERP you can use the :ref:`ch-real` chapter to find out how to create a new workflow from scratch in an empty database with nothing to distract you. Or you can skip directly to the, :ref:`part2-crm-leads`, chapter in the, :ref:`part2-crm`, to start with details of OpenERP's functional modules.

Being an author of several Software Manuals, it is a great challenge to work on the OpenERP documentation and continuously take it to a higher level. Please note that this is a hell of a job, but Els finds great pleasure in doing it!

*From Els Van Vossel*

It acts as a web server to an end user connecting from a web browser, but it also acts as a client to the OpenERP application server.

Is there anything else in the server's history that can help you identify the problem? Open the file \ ``openerp-server.log``\ in \ ``C:\Program Files\OpenERP AllInOne``\ (which you can only do when the server is stopped) and scan through the history for ideas. If something looks strange there, contributors to the OpenERP forums can often help identify the reason.

Although this installation method is simple and therefore an attractive option, it is better to install OpenERP using a version downloaded from http://openerp.com. The downloaded revision is likely to be far more up to date than that available from a Linux distribution.

Maintaining packages is a process of development, testing and publication that takes time. The releases in OpenERP packages are therefore not always the latest available. Check the version number from the information on the website before installing a package. If group differs (for example 7.0) then you may decide to install it because the differences may be minor – bug fixes rather than functionality changes between the package and the latest version.

*You have a choice of approaches for the second operation: either install a web server (most probably on the original server PC) to use with standard web clients that can be found on anybody's PC, or install application clients on each intended user's PC.*

So if you have a team in India and a team in England, the times will automatically be converted. If an Indian employee sets her working hours from 9 to 6, that will be converted and saved in the server's timezone. When the English users want to set up a meeting with an Indian user, the Indian user's available time will be converted to English time.