Properties of applications: Advanced
On the Advanced tab, which is present when you have selected a new or existing application in the Application browser, you determine the more rarely used properties of this application.
Click here for information on how to edit properties in general. On the current tab you'll find the following settings:
Skip list screen if result contains 1 record
This setting is not applicable to Axiell Collections and will be ignored.
This setting is not applicable to Axiell Collections and will be ignored.
Sort the data source list in the Search wizard
This setting is not applicable to Axiell Collections and will be ignored.
Return to first tab when moving between records
This setting is not applicable to Axiell Collections and will be ignored.
Help window visible by default
This setting is not applicable to Axiell Collections and will be ignored.
This setting is not applicable to Axiell Collections and will be ignored.
Show "help" and "return" methods
This setting is not applicable to Axiell Collections and will be ignored.
This setting is not applicable to Axiell Collections and will be ignored.
This setting is not applicable to Axiell Collections and will be ignored.
Leave the welcome screen by pressing any key
This setting is not applicable to Axiell Collections and will be ignored.
This setting is not applicable to Axiell Collections and will be ignored.
Here, choose the interface language you want the currently edited Collections application to start up in when it is started for the very first time or when the user settings have been reset.
Encoding of application texts & Encoding of help texts
The encoding of application texts (system texts) and help texts should be seen separately from the encoding properties of application definitions (.pbk), database definitions (.inf) and screens (.fmt), because system and help texts are located in their own files (.txt and .hlp/.adh), and their encoding can be different from the encoding of the application definition. Their encoding must be indicated here, because Collections needs to know how to represent the characters in these texts on the screen (this is not self-evident to the software).
For existing Collections applications you only need to change the selected character sets for these options if you change the character set in which the text or help files are saved. When you edit these files in e.g. Notepad, you can choose Save as to change the name of the file and/or the character set. Typically you will only change this if in the text you want to add to these files, characters appear that are not supported by the current character set. Do make sure all text files for this application are saved in the same character set, and that all help files are saved in the same character set too.
These options offer the following character sets to choose from: Oem (Western Europe), ANSI (ISO-Latin), and Unicode (UTF-8).
Oem (DOS) is the elementary character set, that cannot represent the € character for instance, ISO-Latin does contain most characters used in western European countries, like the euro-sign; if you need to use more exotic characters, like from Chinese or Hebrew for example, you need to use Unicode in UTF-8 representation.
This option only applies to SQL databases. Fields which you make multilingual in such databases, will be (optionally) multilingual in all the languages which you mark in the current list. (You can always change the selection of offered languages here, without serious consequences.) The user can choose from these languages via the Data language drop-down in the running application.
If you need some special data language that is not present in this list by default, you have the option to add a single custom data language: click here for more information.
It is possible to put all texts used by adapls in one text file (per language), and open the right language variant in the running application automatically whenever an adapl needs to read from a text file, by just providing the name of this .txt file once, here in the application setup. You provide it without indicating the language number in the file.
So, if you have two language text files named adapltexts1.txt and adapltexts3.txt, the name to enter for this option is: adapltexts.txt. Collections will automatically pick the right language file.
The advantage of this option is that you no longer have to open specific text files in adapls before you can read from them. You can just always read from the text file specified here in the application setup.
Here you can provide a (relative) path to an application-specific Help file or to the context.inf file (the latter only if you use a contextual help database instead of .adh files).
By default, .adhHelp files are retrieved from the current application directory, but if you don't want that, you can use this option to specify the folder. Specify the .adh Help file without a language number. Collections will automatically select the right language file when the user opens the Help.
From Collections 1.17, an optional contextual help database and/or Contextual Help application are available. If installed, then simply replace the existing Help texts reference by a reference to the new .inf, so replace e.g. ../texts/applic.adh by ../Contextual Help application 1.0/data/contexthelp.inf.
Feedback
