| 1. | Scrolling Regions
|
| · | All regions in forms are converted to Scrolling Regions in the new R:BASE Turbo V-8 form.
|
| · | When existing form regions are converted to Scrolling Regions in the Turbo V-8 version, any Text Label contained in the region will not appear after the conversion. You will need to manually replace these objects in the R:BASE Turbo V-8 Form Designer after the conversion of the form.
|
| 2. | Push Buttons
|
| · | When converting existing multiple page forms to R:BASE Turbo V-8, if you use Push Buttons with a predefined Next Page or Previous Page EEP, these buttons will appear on the Turbo V-8 form, but will have no action assigned to them. This is because of the Tab Control behavior which is used in R:BASE Turbo V-8 to create multiple page forms.
|
| 3. | Multi-Page Forms
|
| · | All pages on multi-page forms are converted to individual tabs on the Tab Control of the new R:BASE Turbo V-8 form.
|
| 4. | Lookup Variables
|
| · | The "Lookup Variable" is now really a "Lookup Variable", not to be changed. All expressions (if based on lookup variables) are evaluated CORRECTLY and refreshed INSTANTLY. Prior to version Turbo V-8, that was not the case. You had to issue the RECALC command every time you wanted to refresh your variables. If you wish to achieve the same results in Turbo V-8, then DO NOT use form defined expressions, but rather EEPs which can fire when you want and have the freedom to change accordingly.
|
|
|
| Example:
|
|
|
| 1. In the Form Designer, you can create an Exit EEP on the column/variable before the look column/variable field.
|
| 2. Exit EEP should do all the lookup for that column/variable.
|
| 3. Once the value is placed, now you can do whatever you want to change it or keep that same value.
|
|
|
| *TIP - Recently added to the R:BASE V-8 Form Designer was the option to run a command file (or action) for a form before the Form Designer is launched. In the Form Designer, choose "Layout" from the Menu bar, the select "On Before Design Action...".
|
| This allows you to create any variables that Lookup Variables are based upon to avoid annoying error messages when the form is opened in the designer. An example of a lookup variable based upon another variable would be...
|
| 1 : TEXT vCompany = Company IN Customer WHERE CustID = .vCustID
|
| The error message appears because the variable vCustID is not defined. Adding the following to the "On Before Design Action..." will alleviate this error message:
|
| SET VAR vCustID INTEGER
|
|
|
| 5. | Form Variables
|
|
|
| · | Form variables that perform calculations or combine a number of values should be enclosed in parenthesis. If you are getting an error messages for a variables performing calculations, like the one below,
|
|
|
| 2 : CURRENCY vTotal = price * quantity
|
|
|
| add parenthesis as follows:
|
|
|
| 2 : CURRENCY vTotal = (price * quantity)
|
|
|