I looked in to the QlikView API GUIDE documentation and I found actually not one but FOUR different API-calls which can export to HTML from a Macro VBscript (or JScript):
Client-side exports:
ExportHTML
ExportEx
Server-side exports:
ServerSideExportEx
ServerSideExport
The client-side exports actually behaves just like you expect - they are affected by the User Settings where you can switch on or off the thousand seperator on export.
The server-side calls does unfortunately not take this into consideration and will always export without the thousand seperator. The clue to why this is so is also to be found in the API Guide
Simplest and quickest solution:
Depending on how you need to design your solution you might be able to use the ExportEx but save the file to a server file-share which the necessary users that need to run the macro should have write-access to.
Another more elaborate solution that still use the ServerSideExportEx:
Abandoing the HTML as export option but saving it as text - but embedding the necessay HTML to actually get a resulting HTML-file anyway and getting full control of any HTML - still keeping the thousands separator.
I have an example on how this can be done as a QVW if you want to investigate this solution. But it is more time-consuming and it is advisable to have HTML-development competence available...Depending on the setting it will be used it could be less dependable than
the #1 solution.
Conclusion:
The approach chosen depends a lot on the actual environment and the limitations posed by that. So knowing more about which client-side access will be used could be helpful to give further advice: Full Browser, IE Plug-In, QlikView Open-In-Server, tablets.... ?
How will mail be sent? From client-side or is it a server-side component/library? How will it be done? Interactively by the end-users or scheduled by QlikView Publisher or other scheduling mechanisms/products?
