Would like to if there is any development differences if i would like to develop a dashboard which can be used for Desktop users and if deployed for many users in the servers,..
Would there be any differences in the approach of dashboard development.
Refer Qlikview Demo's they are best example to design and develop dash boards in qlikview.
Vikas
Hope this resolve your issue. If the issue is solved please mark the answer with Accept as Solution & like it. If you want to go quickly, go alone. If you want to go far, go together.
Aside from the above suggestions for developing QlikView applications, there are a few differences to keep in mind:
First an foremost: the data stack is different. Although you could put your desktop-oriented model on a QV server as-is, desktop users will most probably have a single integrated script inside the QVW to reload their data, while a server environment usually divides data processing into multiple layers (ODS-QDS-QVW) for reasons of efficiency and economy.
Next and very important when building customized QVWs: macro's can do almost anything in a desktop environment (because that environment is entirely Microsoft-based with office products and email clients readily available) while on the server their range is severely limited. For instance, on the server you cannot change any user interface object programmatically.
Third and something that needs getting used to: Desktop users have a native QlikView UI at their disposal while AccessPoint visitors most often use the AJAX-client (HTML+JavaScript) which is never entirely the same (but it will be "RSN")
Another difference that surprises most starters: on the server, you cannot have a user perform a reload of a document, while in the Desktop environment it's a matter of pressing the standard toolbar button (if enabled).
A difference even further along the road: allowing Desktop users to create their own objects in a QVW is fairly straightforward and they'll get all 1000-options dialogs that every developer gets. In an AccessPoint, there is "shared objects". Access and configuration are entirely different. IMHO still not the most pleasing DIY-toolset, but your mileage may vary.
