I have CAR ,master file. I have a fex file like : ONE.FEX TABLE FILE CAR PRINT * ON TABLE SET ONLINE-FMT HTML END
If i execuet one.fex file, it will return all the rows. My requirement is, If i execute the fex file, i need to see the rows, for which country = FRANCE.
I don't want to limit in the fex file. I want to put that limit in the master file. Please let me know, how can i acheive the same. Thanks ViswakanthThis message has been edited. Last edited by: FP Mod Chuck,
April 13, 2004, 09:15 AM
Mikel
The implementation of Data Source Security in your master file could help..., FILENAME=CAR,SUFFIX=FOC ... END DBA=MIKEL,$ USER=VISWA1, ACCESS=R, RESTRICT=VALUE, NAME=ORIGIN, VALUE=COUNTRY EQ 'FRANCE', $ USER=VISWA2, ACCESS=R, RESTRICT=VALUE, NAME=ORIGIN, VALUE=COUNTRY EQ 'ENGLAND', $ USER=VISWA3, ACCESS=R, RESTRICT=VALUE, NAME=ORIGIN, VALUE=COUNTRY NE 'FRANCE', $
Anyway, using this method, you need add SET PASS=VISWA1 in your fex or profile (not in the report). Otherwise, you will get a security error.
SET PASS=VISWA1 TABLE FILE CAR PRINT * END Regards, MikelThis message has been edited. Last edited by: <Mabel>,
April 13, 2004, 12:24 PM
<Viswa>
Hai Mikel How to add it in the profile? Please let me know Viswa
April 13, 2004, 02:31 PM
<Viswa>
Hai
Let's say i have my report in MRE. And i have a group called grep1. And all the users who are under that group (grp1), when they try to Query that CAR master file, they should be able to see only COUNTRY=FRANCE data.
How can we do this? This is very urgent.Can someone throw some light on this.
Regards, MikelThis message has been edited. Last edited by: <Mabel>,
February 19, 2019, 09:46 AM
Doug
The 'MFD PROFILE' should do the trick. It's new to WebFOCUS 8x, maybe sooner.
I know this is an old thread. But, it came up in a search for something else that was significant. So, I added my Two Cents here for searching.
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
August 26, 2019, 03:53 PM
Mike in DeLand
I will also add to this ancient thread - if you use the DBA security as shown in the answers here, you might consider SET PERMPASS in the profile instead of just SET PASS. That way a user cannot override it. Also you will probably want to disable SQL PASSTHRU since that will bypass your DBA security rules.