Right, the docs seems to be incorrect here (that's not the single instance you've found).
I think you should use it like
COMMENT FIELDS USING FieldCommentMappingTable;
COMMENT TABLES USING TableCommentMappingTable;
TAG FIELDS USING FieldTagMappingTable;
IMHO, there is no real use in defining the fields / tables to comment like COMMENT FIELDA, FIELDB USING .. when using a mapping table (which defines the fields / table names anyway).
Hope this helps,
I agree with your opinion on usability. But then it's not what works that interests me (we get out of these QlikView situations in any case - thank god for that) but what I have to parse to be able to understand all of QlikView load scripts. Building tools is a bit more difficult than writing functioning scripts.
PS a while ago, I submitted an idea to make the QlikView documentation (especially the scripting part) more of an on-line self-correcting, partially user-submitted knowledge base that may include the best of the community examples. You can check it out here (http://community.qlik.com/ideas/2832), and vote if you like it.
Just voted up.
I also tend to nag from time to time about QV documentation, I think your idea would be really a big step forward.
Besides that, I recommend Henrics QV design blog postings, where you can get more insight into QV inner mechanics.
Good luck with trying to understand all QV load scripts, IMHO QV is not as consistent and logical as you expect it.
And the documentation is - say - improvable.