Follow up:
I've realized a better solution might be to create my form at runtime
on the client having a localized version of Outlook. I would still know
an answer on my question but I think a runtime creation of the form
when installing the form is a very nice solution and would allow me to
distribute the same form template to all clients and then modify labels
and core field bindings just before installing the form.
>>
Behind this cryptic subject is the full question:
Is it possible to bind (via code) a core field to a control using the
ItemProperty property even though that core field doesn't exist in the
Outlook DOM?
Here's why I need this. I'm creating multiple localized Outlook forms
and need to bind a field for the "End" time in an Appointment object.
However since core fields are localized I need to change the bindings
for my localized forms (20+ so it's a lot of work).
I've made some code which (using my English Outlook DOM) creates a new
form and sets the labels. Now I need to set the bindings as well using
code such as:
...
MyOwnEndTime.ItemProperty = "End"
...
This works for English and other languages where this core field
exists. However it does not work for Danish:
...
MyOwnEndTime.ItemProperty = "Slut"
...
I makes good sense (unfortunately

, that Outlook checks if it's able
to bind to the field specified, but is it possible to somehow avoid
this validation? I know that my form (when eventually running) will be
in the correct environment (i.e. in the above case, using a Danish
Outlook client).
<<