OPERA TO OPERA II UPGRADE CHECK LIST
Please read this completely before attempting the upgrade from Opera to Opera II.
- Take a backup of all Opera System and Data files.
- Install Opera II assuring the Readme file has been read. The recommended configuration is to have Opera II directories Program, System, and Reports on the server with the local client installs on each client by running the Netsetup.exe. Please note that Opera II will require a shared mapped drive with full access when running Netsetup.
- It is recommended that the upgrade is run from the server, so will require a client install on the server.
- There must be sufficient disk space on the drive volume containing Opera II, for the data to be upgraded.
- Ensure that Opera and Opera II systems are not in use by any users.
- When preparing to run the upgrade you will need to logon to the system, as ‘Admin’. This will give you access to the upgrade wizard in ‘System’, ‘Company Profiles’.
- Ensure that the path in Opera, ‘Company Profiles’ is a relative path; for example, ‘Data’ instead of ‘C:\operaw\data’, and ensure Opera data is on the same drive volume as Opera II.
- If the system has any bespoke programs or data structures, these will need to be updated before the upgrade is run.
Please Note: Should the bespoke data dictionary files not be in place prior to running Update Data Structures for the first time in Opera II, the bespoke data could be lost.
Custom Report Designs
Please refer to Article KB215338 regarding converting Custom layout Designs.
- If Opera has bespoke ‘Modified Report’ designs, these will need to be converted and saved into Visual FoxPro format. Only Opera for Windows not Dos reports will convert.
- Paper sizes and Printer Configuration for continuous Stationery It is important that paper sizes are correctly specified when printing continuous stationery reports. On the Report Layouts form in the System module, the paper length and paper width for a particular layout are specified in 10ths of a millimetre. For standard layouts supplied with your Opera II system, these are predefined. Resellers can find a list of all document paper sizes used on the Pegasus Extranet.
- Specific document designs should be treated as bespoke ‘Modified Reports’. Within ‘Options’ in the Purchase and Sales Ledgers, the document reference will be converted during the upgrade. However, the reports should be converted in Visual FoxPro. Warning: Test all reports thoroughly after the conversion.
- Reporter reports (SEQREPM) are converted during the upgrade. After upgrading, these reports must be run, to convert them into the new format. The reports also need to be re-appended to the menus.
As well as defining paper sizes on the Report Layouts form, the paper size for the printer must be compatible. This means ensuring that any printers identified in the Printer list box on the Report Layouts form that will be used to print continuous-form documents, have their paper sizes set to the layout’s dimensions.For Windows 98 clients, this means using the Paper tab on the printer’s Properties form (displayed via the Windows Printers command). This must be set to use a custom or user defined paper size. The dimensions must then match the ones on the Reports Layouts form.Logon to Opera II as Admin, run the report, when the report design is displayed, select File, Page Setup and select the same paper size as that defined in the Printer Properties. Then close the form which will save the changes made.In the case of Windows NT/2000/XP clients, the same needs to be done, but you use the Form tab associated with the server properties instead.
- Within Opera II, companies should not be set up with the same company ID as any company you are converting from in Opera. If they are set up with the same company ID, the existing Opera company will not be converted. Please be aware some bespoke applications depend on the Company ID.
- There is no requirement for the setup of printers. The system will default to the printers already set up in Windows.
- Check the data for any illegal characters that may have been used. These illegal characters will be removed by the upgrade and replaced by alpha/numeric characters. For example: Test!1, will be replaced with Test01.
- All of the users will need to be re-added after the upgrade, because the SEQUSER will not be converted.
- The timescale for upgrade based on a database of 135MB run across a Network is approximately 3 minutes. Running the update structures will take approximately 25 minutes, assuming no data correction is required. Note: Network traffic must be taken into consideration. Update data structures, is run in three stages: Pre-audit CheckAudit Check / Data Conversion Update Data Structure
When running the Audit Check and Data Conversion, a data validation will be run. If the data is not within the correct conditions, an error screen will appear. This will allow you to correct the data. Please be aware that once the data is changed and accepted, you will not be able to make further changes through Opera II without deleting the company and re-running the upgrade.
Please Note: Ensure that the Screen Saver is deactivated on the machine prior to running the upgrade
Opera II, Upgrade, Opera, Help,
Affected Products & Releases
|Affected Product||Affected Release||Patch Status||Notes|
|PG – Opera II Enterprise||Unknown|
|PG – Opera||Unspecified|
|Recommended Articles for Products :|
|Recommended Articles for Releases :|
|JT-Number/Reference Number :||649|
|Severity :||4 – Low|
|KB Owner :||Unassigned|
|Last Updated :||18 Oct 2005|
Created: 18 Oct 2005 17:40Revised: 18 Oct 2005 17:40