Why use $concat apart from all it’s limitations: it delivers internal format
Have a form with a datim field called X_DATIM.
Set the HELP trigger to:
x_datim = $datim
set the DETAIL-Trigger to:
putmess “Testdatum string: %%x_datim%%%”
putmess $concat (“Testdatum string: “,x_datim)
And you will get in the message frame:
Testdatum string: 11-okt-10 07:14:57
Testdatum string: 2010101107145700
SUccess, Uli
| ulrich-merkel | ||
| Oct 12, 2010 7:46 AM | ||
| I’m fully aware that at the end we get concatenated strings in both ways (and the percent one workes since V4, I suppose). It’s just a hint why $concat may be useful despite of its silly 5 parameters limitation. Success, Uli | ||
 |
||
| richard.gill | ||
| Oct 11, 2010 11:36 PM | ||
| I use both forms: when I’ve too much string substitutions for ‘inplacing’ variables, I prefer use $concat, which is cleaner | ||
|
||
| gypsilon | ||
| Oct 11, 2010 5:26 PM | ||
| %% is string substitution, and that something different to Concatenation. use $concat(“Test”, “%%x_datim”) instead to get the same results. If you use Variables or Fields with a defined Display, the Substitution will take the Display into account, Concatenation will not. | ||
|
||