One can design Crystal Report using different technique. What is the advantage of using database view over Crystal Command? I know stored procedure is a better approach because the code is already compiled. Anyone has any clue about view and command?
A View is a reusable object in that all tools can use it, and it will allow for multiple parameters, so if given the choice, don't consider embedding rules into the client.
A Stored Procedure won't allow for multiple parameters either (well, not without parsing), so if the performance is similar between the View and SP, I prefer the View.
Is there any performance issue between view and command? Right now I am using view considering the fact that we can use it even if we switch to new reporting tool. But View supposed to maintain by Data group. So there is a maintenance issue. But we can maintain report our self.
And I am not sure how do I change data source name if I use command. I don't have repository. But I have three different environments for development, QA and production.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.