Good idea Sami,
I will give it a try.
Esbjorn
One idea in the interim would be to create the charts using a copy of the
database that has had all the rights set to public. Project the tables
you'll need for the charts there. Then you could just copy the RBC files to
the live database. At runtime, from within your R:BASE app, project the
temporary tables, and it should work fine.
Sami
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sami Aaron
Software Management Specialists
913-915-1971
[EMAIL PROTECTED]
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Esbj�rn
Johansson
Sent: Wednesday, March 23, 2005 5:04 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Re: R:Charts Chart based on rows instead ofdatavalues
Javier,
Of course some charts could be based on temporary tables. However, the
problem is not
about what you base the chart on but on the accessability in the
creation-phase. The present
incarnation of R:Charts obviously demands that tables/views are PUBLIC.
This makes it
a bit cumbersome to modernize reports in a production database with an
extensive structure
of granted rights and NO important data accessible for the user
PUBLIC/NONE. There are
of course ways to work around this but my bottomline is that IT SHOULD
NOT BE that way,
it should be possible to connect as a specific user when you connect to
the database from
R:Charts. So, I am looking forward to the next version of R:Charts and
in the mean time I
might revert to old methods like generating data to a file and
launching Excel or whatever.
But now I am off for some holiday celebrations and will be back to the
list next week.
Esbjorn
Esbjorn:
Why don't you base your charts on Temporary Tables, they only exist when
the
user creates them and obviously he would have privileges, nobody else can
have access to them and they are gone when the session ends. Of course,
when
you design the Chart you would have to have the table defined and you
delete
it once the design is completed; then, you just create the temporary table
just before calling the chart.
Javier,
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Esbj�rn
Johansson
Sent: Wednesday, March 23, 2005 2:30 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Re: R:Charts Chart based on rows instead ofdatavalues
Emmitt,
OK I agree on that. However, my problem is in creating the charts when
the underlying
table or view is not public. Of course there is the workaround of making
them public while I
create the charts and that is no problem in the lab. But "in situ" at my
customer's installation
it generates a clash with their security guys. So I am looking forward
to the next release of
R:Charts, where this inconvenience will probably have disappeared.
Regards,
Esbjorn
Esbjorn,
As I do not work with R:Base's internal security (OWNER = PUBLIC) I
cannot give you an absolute on your question. My point was that once
the chart is created security should not be an issue as the user
running the chart will only have access that pertains to their
permissions.
Hi Emmitt
Regarding point 3 below:
Are you saying that if I have a multi-user R:Charts, I will then be
able to start R:Charts
and connect to a database as a specific user-ID that is NOT PUBLIC
but have access rights
to the table that is to be the basis for my chart?
I would be VERY happy if that is the case.
Esbjorn
It seems that 3 reasonable enhancements to the basick R:Charts
would be:
1. ability to use R:Charts while connected with R:Base....
If you have purchased a multi-user version of R:Charts this is no
problem. I can work in the R:Charts designer while the db is open
with MULTI ON and STATICDB ON.
2. The ability to pass "Where" conditions as part of the chart.
For my part this is a non-starter....
3. The ability to set users to deal with R:Base security
implementations.
Again, if you follow the strictures in 2. above, this is a non-starter.
Emmitt Dove
-------------
Esbj�rn Johansson
<[EMAIL PROTECTED]>
Emmitt Dove
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT 06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]
__________ NOD32 1.961 (20041230) Information __________
This message was checked by NOD32 antivirus system.
http://www.nod32.com
__________ NOD32 1.961 (20041230) Information __________
This message was checked by NOD32 antivirus system.
http://www.nod32.com
__________ NOD32 1.961 (20041230) Information __________
This message was checked by NOD32 antivirus system.
http://www.nod32.com
