topic Macros in QlikView https://community.qlik.com/t5/QlikView/Macros/m-p/898480#M530566 <HTML><HEAD></HEAD><BODY><P>Hi Folks,</P><P>I would like to know your statements for the use of macros.</P><P></P><P>I know that macros should be used with care. The document " ... Macros are bad" (sorry I donot know the author) describes</P><P>the risks. We reduced the macros already and only DefineClearState and Zooming are still in our apps.</P><P>Now Hosting forbids the use of macros in general. They say that zooming can be achieved using the menu and defineclearstate can be achieved by using a button and defining actions.</P><P>This is true, but the user has more clicks to achieve the same behaviour (my opinion is to make it easier for the user</P><P>as long as the application is easy to handle)</P><P>One argument is that the clear button (with fields defined) takes more performance than a button with actions (eg I need 11 actions to get the same behaviour).</P><P></P><P>Are they talking peanuts or are there real issues behind?</P><P></P><P>any opinions on that?</P><P></P><P>Regards</P></BODY></HTML> Tue, 07 Jul 2015 11:47:49 GMT Anonymous 2015-07-07T11:47:49Z Macros https://community.qlik.com/t5/QlikView/Macros/m-p/898480#M530566 <HTML><HEAD></HEAD><BODY><P>Hi Folks,</P><P>I would like to know your statements for the use of macros.</P><P></P><P>I know that macros should be used with care. The document " ... Macros are bad" (sorry I donot know the author) describes</P><P>the risks. We reduced the macros already and only DefineClearState and Zooming are still in our apps.</P><P>Now Hosting forbids the use of macros in general. They say that zooming can be achieved using the menu and defineclearstate can be achieved by using a button and defining actions.</P><P>This is true, but the user has more clicks to achieve the same behaviour (my opinion is to make it easier for the user</P><P>as long as the application is easy to handle)</P><P>One argument is that the clear button (with fields defined) takes more performance than a button with actions (eg I need 11 actions to get the same behaviour).</P><P></P><P>Are they talking peanuts or are there real issues behind?</P><P></P><P>any opinions on that?</P><P></P><P>Regards</P></BODY></HTML> Tue, 07 Jul 2015 11:47:49 GMT https://community.qlik.com/t5/QlikView/Macros/m-p/898480#M530566 Anonymous 2015-07-07T11:47:49Z