Browsing Hawaiian translation

511.

Locate the separate server executable ``openerp-server.exe`` (this is not the executable used by the Windows Service!). It should be in the location where you installed OpenERP Server, for example in ``C:\Programs\OpenERP 6.0\Server``.

512.

From a Command-Line Prompt, start the server executable manually (directly call the executable you located above), with the following parameters, to trigger an update of all module data and views in the database, based on the new source files (include your usual startup parameters, if any, and replace ``DB_NAME`` with the name of the OpenERP database you wish to update)::

513.

Let the server complete its startup (watch the log file for the final message that says ``OpenERP server is running, waiting for connections`` or wait until you can connect to that database with a GTK client), then stop the server using the :kbd:`Ctrl+C` key combination and repeat previous step for each database on this OpenERP installation (any database not updated will use the latest business logic but might have errors or missing improvements in the views until you update it using this procedure).

514.

Stop the server again with :kbd:`Ctrl+C` and restart it normally as a service.

515.

You can now proceed with the update of the GTK clients, which can be done separately by simply reinstalling the latest version over the previous one.

516.

As an alternative to restarting the server in update mode for each database, as described above, you may try to start the server normally after installing the new version, and then connect to each database as the *Administrator* user, open the list of modules and manually trigger an update of the *base* module.

517.

Because all modules depend on *base* they will be updated too. However this requires the *Administrator* password of each database and may not work for some updates, specifically when the update prevents you from logging into the system.

518.

OpenERP's release policy states that one or two major releases are published from the development version every year. Transitioning to the next major release implies a lot more changes than jumping to another minor release. As the underlying OpenERP data structures usually evolve quite a bit from one major release to the next, a full migration of the existing data is needed. Each major release will be published with specific recommendations and procedures for upgrading an existing OpenERP system to the next major version.

519.

Major Release

520.

For major releases, it is usually not possible to skip one release, for example upgrading directly from OpenERP 4.2 to OpenERP 6.0. If you need to do such an upgrade, you will simply have to do each intermediary upgrade one after the other.