Report Root Folder(%rsroot%) = "C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services"

http://localhost/reports => "C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager"

http://localhost/reportserver =>"C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer"

    * Edit Styles [%rsroot%\ReportServer\Styles]
         1. HtmlViewer.css
               1. Css Class = ".MenuBarBkGnd"
                  Type = "background-color"
         2. SP_Full.css
               1. Css Class = ".MenuBarBkGnd"
                  Type = "background-color"
         3. SP_Small.css
               1. Css Class = ".MenuBarBkGnd"
                  Type = "background-color"

    * Replace [%rsreports%\ReportManager\images\TOOLGRAD.GIF] with you image (keep imagename as "TOOLGRAD.GIF")

    * Edit Style [%rsroot%]\ReportManager\Styles]
         1. ReportingServices.css
         2. RSWebParts.css

Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

Cause:

Anything that access database from SP requires at least the WSS_Medium security policy in the web.config file. If you receive a security message from the web part, it's usually the trust element in the web.config file.

Fix:

Open wss_mediumtrust.config & wss_minimaltrust.config usually (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\config\) look in your web.config file for the exact
path.

Find in wss_mediumtrust.config: <SecurityClass Name="SqlClientPermission" Description="System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>

Copy and paste it in to the <SecurityClasses> node of wss_minimaltrust.config.

In the PermissionSet section of this configuration file, add the following:

Find in wss_mediumtrust.config: <IPermission class="SqlClientPermission" version="1" Unrestricted="true"/>

Copy and paste it in to the a <PermissionSet> node of wss_minimaltrust.config.

That about covers it.

OR

The application pool aslo has db owner permision to pubs.

◊ CSS Reference Chart for SharePoint 2007 (Microsoft Office SharePoint Server 2007 and Windows SharePoint Services v3) Link

◊ Image Reference Guides for SharePoint 2003 Link

◊ Page CSS Element Link

◊ Master Page Element Link

◊ How to: Create a Minimal Master Page Link | DefaultPPY.master (5.45 kb)

SharePoint Tips :

1. Hide the Site Settings Link in Portal?
   

   To quickly hide the Site Settings link in portal, add this to your custom style sheet:
   
   #SettingsOrReturnURL {display: none}
   
   All this does is change the display of the link itself to none.  So you aren't actually removing it from the code.
   

Introduction:

The following SharePoint Application Page with C# in line code enumerates all the roles assignments of a Windows SharePoint Services 3.0 or MOSS site collection and displays pirticular web site from which the page has been called:

• The role member and reports if it is a Group or an User.
• If it is a group, displays the number of users in the Group and the users list.
• If it is a group, displays the permissions for all significant Site Collection elements (if inheritance was broken for a List, a Folder or an Item, this will be specified). It is information at a cross-site level.
• In any case (User or group), displays the Roles list for the current web site.
• In any case (User or group), displays for each previous roles, the Roles Permissions list.

This post and its code sample is an improvement of the previous post Enumerate Role Assignments to retrieve Groups and Users Permissions in a Windows SharePoint Services 3.0 or MOSS Site . I also did this new post to help a reader that has asked me information about SharePoint Roles and Permissions reporting.

Why to use it?

In Windows SharePoint Services 3.0, access to Web sites, lists, folders, and list items is controlled through a role-based membership system by which users are assigned to roles that authorize their access to Windows SharePoint Services objects.

To give a user access to an object, you can do so either by adding the user to a group that already has permissions on the object, or by creating a role assignment object, setting the user for the role assignment, optionally binding the role assignment to the appropriate role definition with base permissions, and then adding the assignment to the collection of role assignments for the list item, folder, list, or Web site. If you do not bind the role assignment to a role definition when assigning a user to a role, the user has no permission.

As there is two ways of granting permissions to a specific user, this can easily lead to a lack of organization regarding Security Granting Policy, and you may have some SharePoint sites to clean up.

When you want to check the users and the groups present in a Site Collection web sites and their role, it can take time doing it by browsing "People and Group" administration pages for each web site. It would be nice to display all the information in a single report. The following code sample will give you this kind of report, and it will be easier for you to reorder Users and Groups using it.

How to use it?

• Download CheckUsersAndPermission.aspx file to "%12%\TEMPLATE\LAYOUTS"
• Add "<asp:MenuItem Text="Advanced User Permission Details" NavigateUrl="checkUsersAndPermission.aspx" />", after "<asp:MenuItem Text="<%$Resources:wss,people_sitepermissions%>" NavigateUrl="user.aspx"/>" for the following files in "%12%\TEMPLATE\LAYOUTS"
  • people.aspx
  • user.aspx
  • groups.aspx
• Now you can go to any site>People and Groups, on left Site menus you can see
  

File(Source Code) : CheckUsersAndPermission.aspx (18.87 kb)

File(Source Code) : CheckUsersAndPermission.aspx (18.87 kb) (Version2)

thanks to Marc Charmois

If you have a multi-language site, you have probably already worked with .resx files.  Resx files are resource files that can contain strings, images, sounds... pretty much anything.  However, in ASP.NET (at least in our typical scenarios), resource files mainly contain strings to be translated in multiple languages.  Those needing a refresher course on ASP.NET localization should take a peek at this article: ASP.NET Localization. Let us take a typical ASP.NET application as an example.  When you generate a resource file for a file named Default.aspx, VS.NET generates a new folder named App_LocalResources (if it doesn't exist) and it creates a new file named Default.aspx.resx in this folder.

This option will only be visible in the design view of an aspx or ascx file.

Default.aspx.resx will contain all strings that can be localized from Default.aspx.  Default.aspx.resx is the default resource file for Default.aspx.  It will contain the default language strings, in our case English.  Should you need to offer the same application in more than one language, you will need to create locale-specific resource files with a similar filename. For example, Default.aspx.fr-CA.resx would be a resource file for Canadian French. The logic to retrieve a string from the appropriate resource file is built into the .NET framework (it depends on the current thread's culture).

Those who have built a dynamic web site supporting multiple languages know that managing resx files is a burden, especially when the application changes.

For more read this

Source : ResXEditor.zip (1.01 mb)

thanks to RESX file Web Editor

Related Technologies

• GridView: Bulk Editing
  • Real World GridView: Bulk Editing : http://blogs.msdn.com/mattdotson/articles/490868.aspx
  • ASP.NET Real World Controls : http://www.codeplex.com/ASPNetRealWorldContr
  • How To Use BulkEditGridview To Save Hours In Database Editing : http://dotnetdiscussion.net/.....-database-editing
  • Source : RealWorldGrids.zip (89.79 kb), BulkEditGridView.zip (7.27 kb)