If you're talking about Impromptu, the answer is Yes. The only access control left is at the database level, based on the userid that made the connection to the database.
If you have only one or two reports that need free-hand SQL, then this can be a handy way to get the job done without modifying the catalog. But as you probably noticed, once you enter SQL directly, you lose much of the usual user interface for creating and modifying reports. And you lose the catalog-level access control.
In the end, you may find it cleaner to just modify the catalog to include whatever additional data items you were introducing with free-hand SQL. Then you get your catalog access conrol and report-modifying interface back. Downside is that you will have to maintain a modified catalog from now on.
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.