Re-create the Show Desktop Icon

To re-create the Show desktop icon yourself, follow these steps:

1. Click Start, click Run, type notepad in the Open box, and then click OK.
2. Carefully copy and then paste the following text into the Notepad window:
   [Shell]
   Command=2
   IconFile=explorer.exe,3
   [Taskbar]
   Command=ToggleDesktop
3. On the File menu, click Save As, and then save the file to your desktop as "Show desktop.scf". The Show desktop icon is created on your desktop.
4. Click and then drag the Show desktop icon to your Quick Launch toolbar.

To Get User's IP Address ASP.Net C#

            // Get request.
     HttpRequest request = base.Request;

     // Get UserHostAddress property.
     string address = request.UserHostAddress;

Time Changes What’s Important

“The key is in not spending time, but in investing it.” — Stephen R. Covey  

One of the main reasons To Do lists, backlogs, and lists of all the things you need to get done rots over time is because time changes what’s important.

That’s a good thing.

Because time changes what’s important, it’s a do a reset and a re-think on what your next best thing to do is.  Before you just grab things from your lists or from your backlog, ask yourself a few questions:

1. Is this still relevant?
2. Is this still important?
3. Is this my next best thing to do?

This is a quick way to step back and take a look from the balcony.  By asking if this is still relevant or still important, you can let things slough off and free yourself up for doing stuff that matters.  Letting stuff slough off makes space for the great stuff.

By asking if this is your next best thing to do you’re asking a question about windows of opportunity.   It’s true that a stitch in time saves nine, and you really can miss the boat for some things.  By paying attention to your windows of opportunity, you can get time on your side.

Quoted from : http://sourcesofinsight.com

The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine?

The error occured in an asp.net application while trying to upload data from an excel file to a database.

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.

Solution

Downladed the 2007 Office System Driver: Data Connectivity Components and installed on the hosted server and the issue was sorted.

The 2007 Office System Driver: Data Connectivity Components could be downlaoded from the following link http://www.microsoft.com/downloads/en/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en

Google Changes Search Algorithm

Google Changes Search Algorithm

Unprotect a Protected Excel Workbook

To unprotect a protected workbook all you have to do is to run this macro on the protected workbook. It really worked on me.

Happy Endings !





Sub PasswordBreaker()
    'Breaks worksheet password protection.
    Dim i As Integer, j As Integer, k As Integer
    Dim l As Integer, m As Integer, n As Integer
    Dim i1 As Integer, i2 As Integer, i3 As Integer
    Dim i4 As Integer, i5 As Integer, i6 As Integer
    On Error Resume Next
    For i = 65 To 66: For j = 65 To 66: For k = 65 To 66
    For l = 65 To 66: For m = 65 To 66: For i1 = 65 To 66
    For i2 = 65 To 66: For i3 = 65 To 66: For i4 = 65 To 66
    For i5 = 65 To 66: For i6 = 65 To 66: For n = 32 To 126
    ActiveSheet.Unprotect Chr(i) & Chr(j) & Chr(k) & _
        Chr(l) & Chr(m) & Chr(i1) & Chr(i2) & Chr(i3) & _
        Chr(i4) & Chr(i5) & Chr(i6) & Chr(n)
    If ActiveSheet.ProtectContents = False Then
        MsgBox "One usable password is " & Chr(i) & Chr(j) & _
            Chr(k) & Chr(l) & Chr(m) & Chr(i1) & Chr(i2) & _
            Chr(i3) & Chr(i4) & Chr(i5) & Chr(i6) & Chr(n)
         Exit Sub
    End If
    Next: Next: Next: Next: Next: Next
    Next: Next: Next: Next: Next: Next
End Sub

Recovering From A Suspect Database

Recovering From A Suspect Database


Tormented problem that occurred due to database showing as suspect could be recovered with a hope of luck. Various articles on the WWW depict the similar T-SQL queries to be run on the suspected database. Simply the suspected database could be restored with the latest backup available and could solve the issue in minutes. Worst case scenario you will not have a back up or the latest back up is taken after the database mode has already gone to suspect mode.


We really came across the worst case scenario to one of our most critical database. We purchased a software (recovery tool for sql server) which created scripts which could be executed to populate the tables and data from the suspected data backup. Believe me running them is a task.


Why this suspect mode in a database does occur?


Actually to our scenario we really could not find the real answer why. But we suspect to be the low disk space in the server.


During a WWW search I found these...


A database can be marked suspect for one of the following reasons (this is from SQL Server Books Online):

• If one or more database files are not available.

• If the entire database is not available.

• If one or more database files are corrupted.
• There is not enough space available for the SQL Server to recover the database during startup.

• Database cannot be opened due to inaccessible files or insufficient memory or disk space.

• Database files are being held by operating system, third party backup software etc.

• Unexpected SQL Server Shutdown, Power failure or a Hardware failure.

How you could recover?


Run this query


USE Master

GO


-- Determine the original database status



SELECT [Name], DBID, Status

FROM master.dbo.sysdatabases


GO


-- Enable system changes


sp_configure 'allow updates',1


GO

RECONFIGURE WITH OVERRIDE


GO


-- Update the database status


UPDATE master.dbo.sysdatabases


SET Status = 24


WHERE [Name] = 'YourDatabaseName'


GO


-- Disable system changes


sp_configure 'allow updates',0


GO


RECONFIGURE WITH OVERRIDE


GO


-- Determine the final database status


SELECT [Name], DBID, Status


FROM master.dbo.sysdatabases


GO


We ran this on on our suspect mode database. But there occcred a situation where it did not display any tables after some time. But mode of the database has been chaged from suspect mode. We did this several times. With some luck this would correct the problem. But to our scenario the recovered database could not be backed up. So what we did was made a DTS transfer to another database. And made a scripts of the sp’s, views, indexes and constraints and built up simultaneous database to bring back the database with the most current data.