Open modes that are not supported are replaced by the Normal Open mode. The Fast and Damaged Open modes are not supported for all data source types, and the Reindex Open mode is not supported for SQL data sources. The task's various forms are placed in the task's Form Editor.ĭB Table entries that are not used in the task are replaced by Declare operations in the task's Data View Editor. The task's logic is placed in the task's Logic Editor. The Main Source definition, link declarations and variable definitions are moved to the task's Data View Editor. The project information is saved in XML source files. In Magic xpa, the project information is no longer saved as an MCF. The Export Document option was removed from the Operation list in the Export/Import dialog box. The Multi User Access environment setting is no longer supported. The Internet tab is removed from the APG dialog box. The Internet APG for a table or task is no longer supported. The Internet Development File Root application property is no longer supported. The Java option from the Browser client technology environment setting is no longer supported. The following Magic.ini settings were removed from the MAGIC_DBMS section: The following columns have been removed from the DBMS repository: The XA Transactions property was removed from the SQL tab of the Database Properties dialog box. The Common Data Dictionary property was removed from the Options tab of the Database Properties dialog box. The Magic Server column was removed from the Database repository. This was changed and now the table width is not affected by the visibility of the columns. In V9.4 Runtime, when a column was hidden due to a change in the column’s Visible property, the table width was decreased. The HTML Merge Interface Type is now named Merge. The Internet Development File Root property has been removed from the Project properties. The HTML class has been removed from the Model repository. The HTML property has been removed from the Style section of the property sheet of variables, columns and models. We recommend that you remove any form of this type before exporting your application. Magic xpa does not support forms with the HTML interface type. Web Online is not supported in Magic xpa.įorms with the Web Online Response interface type are not supported in Magic xpa.ĭuring the conversion, these types of forms will be removed from the application, and any Form Output operation pointing to these forms will not point to a form in the converted project.
Unipaas subfurm status code#
In development, Magic xpa provides Version Control support for any third-party Version Control product that uses the SCC (Source Code Control) API V1.01, such as Visual SourceSafe and PVCS. Magic xpa does not use the MVCS mechanism. The act_std_V9.eng file maintains the eDeveloper V9 shortcuts and the act_std.eng file provides Microsoft® Windows® compliant key combinations. Magic xpa provides two keyboard mapping files. The Magic xpa Single User Edition does not include the usrupd.exe utility. In Magic xpa you can only assign runtime rights. is the name of your current file name and is the name that you want given to the file that is created by the usrupd.exe utility. You do this by running the usrupd.exe utility from the command line. If you want to use your security file (such as usr_std.eng) from previous versions, you need to convert your existing security file. If you used non-TrueType fonts in your application, replace those fonts in the Font table from a non-TrueType to a TrueType font. Since version: 2.4 (In previous 2.x versions, font orientation was not supported.) Only TrueType and limited Open Type fonts are supported.įont orientation is only supported for Label controls and column headers. To migrate your fonts and colors to Magic xpa, use your current color and font files as the Runtime Application color and font definition files of the Magic xpa application. You should search for the string VarAttr to see where it is equated with 'M'. The conversion process will not automatically change expressions with the VarAttr function. The VarAttr function will no longer return 'M' for Memo as this is no longer a Magic xpa attribute. Note that during the conversion process, information in non-supported properties will be lost.Īny variable with a Memo attribute is changed to an Alpha attribute.ĭatabase fields that had Memo attributes will be converted to Alpha attributes with Memo storage. For the differences since uniPaaS V1, see Differences Between V1.9 and Magic xpa 2.5. The major differences between eDeveloper V9 and uniPaaS V1 are described below. Differences Between eDeveloper V9 and uniPaaS V1