Hi Kristof,
There are a couple of things worth mantioning here
>> We don't want different exe-files per customer.
of course not - that would be insane.
first thing to be aware of is that the xHtml entries come with a "condition". Meaning that if you have 3 cases, it's trivial to put those cases into the condition, and have 3 entries in the xHtml tab. For example, a few of the examples do this with the header. You can have a different header to be displayed if the user is logged in, or logged out.
The second thing of interest here is that your xHtml is very short. So it becomes practical to examine the generated code to see how it is generated. It's basically just a routine, and the routine is called once from the code. From here it's a hop, skip and sneeze to just embedding your own routine (in source code) and making a call to the routine, also from embed code.
The routine is just building a string, so normal Clarion string handling applies - as does normal file handling, so you can easily read the file here, and inject your string into the string is easy.
The last alternative, and the one you probably want to use, is the ability to inject a session value into the HTML. For example;
<div class="nt-left nt-site-header-logo"><img src="<!-- Net:s:someimage -->" />
You could set the session value ("someimage") when the person logs in.
Cheers
Bruce