Thank you both for your reply.

That is the case.

What I've read sofar, using the Razor Host module is more flexible than creating a 'normal' module. (Only disadvantage seems to be that you have to log in as a host to be able to adjust the content.)

What I was hoping when initially writing this post, was that it would be possible to create some sort of user control that contained the code linking to the database and then using this user control in e.g. the Html module. So a 2 layer approach. But this or something similar can't be done at the moment in DNN, can it? (The thing that comes closest is probably the Razor Host module, but that is not really a 2 layer solution.)

To my knowledge I would have to recompile the module each time I adjust even a single character / word and reupload it to my webhoster. That seems less flexible than the Razor solution. Or am I mistaken?

Or I could implement a similar structure (with native asp.net code embedded into HTML markup) like the Razor Host module already provides. Or am I overlooking something?

On another note - if you build a module using the WSP development style there is actually no need ever to compile the code - since the ascx file and ascx.vb file all live on the server and are compiled at runtime as needed.

Using this model you get all the benefits of module development - without the overheads of razor.

One thing to understand is that every module be it WAP or WSP based are eventually compiled down into CLR p-code - which leads to performance and executing improvements = meaning once a page is visited and executed once during a session it wont need to be recompiled unless the server see a change to the source or in the case of a WAP module needs to be reinterpreted and when a new dll is uploaded to the bin folder.  

Razor code is compiled effectively line by line on the fly every time a page is requested - its not designed for performance but instead for quick functionality.

Westa