SharePoint 2010 conditional formatting for lists

The below was exactly what I was about to blog about, no need to repeat it!


Bander's Blog Post:
SharePoint Lists Conditional Formatting using SharePoint Designer 2010
Thanks!

Security Tip: SharePoint 2010 Access to all users (Authenticated users)

Site Actions -->
Site Permissions -->
Grant Permissions -->
Select Users --> NT AUTHORITY\authenticated users


What happened to Add All Authenticated Users?

Anti-Secuity Tip: Really simple iOS Passcode

1) Enable (Simple Passcode) option, so that your code can constitute 4 numeric digits only.

2) Simplest Passcode to enter is: 2 5 8 0. Four digits is a vertical line.

Tip:
- This post is not a security post as the name implies.
- This post is useful in similar cases when you register Exchange account with a policy to have a passcode; however, you are sure that your device is secure and you do want to have the least interruption with the passcode screen.

OLE DB error: OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.

Error Message:
OLE DB error: OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.

Tools:
SQL Server Data Tools for SQL Server 2012
Microsoft SQL Server 2012 

Scenario:
Using the above tools to create  a cube in a new business analysis solution, I was getting the top error when I try to process the cube. Finally I discovered that the issue was that I am using provider Native OLE DB\SQL Server Native Client 11.0 while the DB acceptability was SQL Serevr 2005 (90).

Resolution:
this can be solved by reverting to the provider Native OLE DB\SQL Server Native Client 10.0