Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Securing Access and Excel ODBC Data Sources

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Securing Access and Excel ODBC Data Sources
 Login/Join
 
Eric Martin
Member
posted
If you have a few Master Files out there that are using Access or Excel as data sources then what have you found to be the best way to secure these Master Files or make them available to only a specfiic group? I've looked at the RESTRICT option and creating user profiles but these seem to be administrative intensive. I thinking about creating a dynamic fex that would be executed within the edasprof but want to make sure this is a best practice or not. Please advise on any information you may have pertaining to this issue.

thanks,
Eric


Prodcution: 713
Test: 717
Windows Server 2003 R2SP2 Standard
 
Posts: 8 | Location: Houston | Registered: May 01, 2003Report This Post
dhagen
Virtuoso
posted Hide Post
User profiles would be the recommended way, but having said that, you could use your fex idea, but don't put it in the edasprof. Depending on your release, the edasprof will not execute any dialog manager commands (older releases will, but newer releases will not). Use the _site_profile setting in the client admin console to call your control fex. Keep in mind also, that this may not be the best way, as the _site_profile is not called for ReportCaster requests.


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
Eric Martin
Member
posted Hide Post
Ok, thanks for the recommendation. I need for this setting to take effect in ReportCaster Jobs also. Seems like taking the profile approach maynot be a bad idea afterall.

thanks,
Eric


Prodcution: 713
Test: 717
Windows Server 2003 R2SP2 Standard
 
Posts: 8 | Location: Houston | Registered: May 01, 2003Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Securing Access and Excel ODBC Data Sources

Copyright © 1996-2020 Information Builders