Translations by Carl Leitner

Carl Leitner has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.

5162 of 62 results
59.
Row will not be dropped if form is not found
2012-07-04
La riga non verrà eliminata se il modulo non viene trovato
2010-12-13
Row will not be dropped if form is not found
60.
An internal key used to identify the form relationship. It may not be the same as the key for any of the existing named forms in this relationship.
2012-07-04
Una chiave interna utilizzata per identificare il modulo della parentela. Potrebbe non essere la stessa chiave utilizzata per gli altri moduli indicati in questa parentela.
2010-12-14
An internal key used to identify the form relationship. It may not be the same as the key for any of the existing named forms in this relationship.
61.
Please select either a form to use as the primary form for this form relationship or choose to copy an existing form relationship to a new one by clicking on the appropriate Options link below.
2010-12-13
Please select either a form to use as the primary form for this form relationship or choose to copy an existing form relationship to a new one by clicking on the appropriate Options link below.
62.
Please select a form to use as the primary form for this form relationship by clicking on the Options link below.
2010-12-13
Please select a form to use as the primary form for this form relationship by clicking on the Options link below.
63.
An internal key used to identify the form relationship. It may not be the same as the key for any of the existing form relationships.
2010-12-14
An internal key used to identify the form relationship. It may not be the same as the key for any of the existing form relationships.
64.
To construct a new form relationship, you will need to first choose a Primary Form
2010-12-14
Per costruire una nuova form relationship, devi scegliere per prima cosa un Form primario
65.
A description of the relationship that should be understandable to the end user.
2010-12-13
Una descrizione della relationship che deve essere comprensibile all'utente finale.
66.
The defining SQL for this function. You refer to a form with the name <formname> and the field <field> `<formname>+<field>` in your function.
2010-12-14
The defining SQL for this function. You refer to a form with the name <formname> and the field <field> `<formname>+<field>` in your function.
67.
The name of the form that is displayed to the end user. If none is specified, then the short name (
2010-12-14
Il nome del form che verrà visualizzato dall'utente finale. Se non ne esiste nessuno specificato, allora il nome corto (
74.
The fields that are linked when listing options. Only applies if the form field is a subclass of I2CE_FormField_MAPPED. It should be a colon separated list of 'forms' or 'form+linkfield's. Example: "county:district+region:[region]:country". If not set, it defaults to the name of this function.
2010-12-14
The fields that are linked when listing options. Only applies if the form field is a subclass of I2CE_FormField_MAPPED. It should be a colon separated list of 'forms' or 'form+linkfield's. Example: "county:district+region:[region]:country". If not set, it defaults to the name of this function.