Following script will be useful to highlight the data available in the Web application textbox.

Set WshShell = CreateObject("WScript.Shell")
wait(1)
Browser("info").Page("info").WebEdit("uname").Set "Ramu"
wait(1)
Browser("info").Page("info").WebEdit("uname").FireEvent "onfocus"
WshShell.Sendkeys "^a"

Set BrowserObj = Description.Create   
    BrowserObj("micclass").Value = "Browser"   
    Set Obj = Desktop.ChildObjects(BrowserObj)    
    For i = Obj.Count-1 To 0 Step -1  
           Obj(i).Close  
     Next

Despite of hundreds of web articles on Smoke and sanity testing, many people still have confusion between these terms and keep on asking to me. Here is a simple and understandable difference that can clear your confusion between smoke testing and sanity testing.

Here are the differences you can see:

SMOKE TESTING:

• Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
• A smoke test is scripted, either using a written set of tests or an automated test
• A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
• Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
• Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

SANITY TESTING:

• A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
• A sanity test is usually unscripted.
• A Sanity test is used to determine a small section of the application is still working after a minor change.
• Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
• Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

Hope these points will help you to clearly understand the Smoke and sanity tests and will help to remove any confusion.

Use the below code to compare Two Excel files data
Keep the below code in .vbs file and just double click on the .vbs.
provide path of the excel files with extension .xls
you can run the below script both in .vbs as well as in QTP Script
---------------------------------------------------------------------
ExcelFilePath1 = InputBox("Please Enter the Path of first Excel File")
   Set fso = CreateObject("Scripting.FileSystemObject")
   If (fso.FileExists(ExcelFilePath1) = false )Then
   msgbox  ExcelFilePath1 & " doesn't exist."
wait(2)
   wscript.quit
   End If

ExcelFilePath2 = InputBox("Please Enter the Path of second Excel File") 
If (fso.FileExists(ExcelFilePath2) = false )Then
   msgbox  ExcelFilePath2 & " doesn't exist."
   wscript.quit
End If

Set objExcel = CreateObject("Excel.Application")
objExcel.Visible = false
Set objWorkbook1 = objExcel.Workbooks.Open(ExcelFilePath1)
Set objWorkbook2 = objExcel.Workbooks.Open(ExcelFilePath2)
Set objWorksheet1= objWorkbook1.Worksheets(1)
Set objWorksheet2= objWorkbook2.Worksheets(1)
For Each cell In objWorksheet1.UsedRange
     If cell.Value <> objWorksheet2.Range(cell.Address).Value Then
    'Highlights in green color if any changes in cells (for the first file)
           cell.Interior.ColorIndex = 4
 'Highlights the same cell in the Second file
 objWorksheet2.range(cell.Address).interior.colorIndex = 4                 
 Else
       cell.Interior.ColorIndex = 0

  End If

Next
ObjExcel.displayAlerts = False 
objExcel.Save
objExcel.quit
set objExcel=nothing
msgbox "It is Done"

Let me know if any you get error while trying to execute the same

Use the following code to capture screenshot of the browser and to place the file in a seperate location

----------------------------------------------------------------------------
Browser("title:=TNSInfo Login").Page("title:=TNSInfo Login").WebEdit("name:=password").Set "Palanki"
Browser("title:=TNSInfo Login").CaptureBitmap "C:\New.bmp",True

We can capture the StatusText of the Browser with the following script

msgbox Browser("title:=Gmail").Object.StatusText

Following statements will helps you to send mail automatically through QTP.
For that you need to have a MS Outlook with mail server connected to it in your machine

Dim objOutlookMsg
Set objOutlook = CreateObject("Outlook.Application")
Set objOutlookMsg = objOutlook.CreateItem(0)
objOutlookMsg.To = "ramu.palanki@gmail.com"
objOutlookMsg.BCC ="ramu.palanki@gmail.com"
objOutlookMsg.Subject = "Sending Mail through QTP Script"
objOutlookMsg.Body ="Hello QTP"
objOutlookMsg.Attachments.Add("C:\Result.html")
objOutlookMsg.Send

Following script will create an Excel file and types some value(Hello) and saves it in C Drive

Below code will be helpful for creating  and closing excel sheet

Dim xlApp
Dim xlBook
Dim xlSheet

Set xlApp=CreateObject("Excel.Application")
Set xlBook=xlApp.workbooks.add
Set xlSheet=xlBook.activesheet
xlSheet.cells(1,1)="helloo"


xlBook.saveas "C:\test.xls"
xlApp.quit

Reporter Object is used for sending information to the test results. With the help of this object you can:

• Report the status of test results (like pass, fail, warning)
• Enable/Disable reporting of step(s) following the statement.
• Retrieve the folder path in which the current test's results are stored.
• Retrieve the run status at the current point of the run session.

There are some very important methods and properties associated with it.

ReporterEvent Method:

I think this is a very common method used with Reporter object. I am sure even if you have worked on QTP for a relatively short period, you would have come across this.

Its syntax:

Reporter.ReportEvent EventStatus, ReportStepName, Details

where EventStatus can be:

0 or micPass: If this step runs test passes which is shown in test report.

1 or micFail: If this step runs test fails which is shown in test report.

2 or micDone: Used to send message to the test report and does not affect status of test.

3 or micWarning: Again, used to send warning message to the test report and does not affect status of test.

and

ReportStepName is name of step

and

Details are the user defined details for the given step.

For Example:

Reporter.ReportEvent micPass, "Login Authorization", "The user-defined step passed."

Filter property

There can be situations where you don't want the full status displayed on the test report. This property can be used to selectively filter the status of your tests.

Its syntax:

Reporter.Filter = NewMode

where NewMode can be:

0 or rfEnableAll: This is the default mode. All reported events are displayed in the Test Results.

1 or rfEnableErrorsAndWarnings: Only those events with a warning or fail status are displayed in the Test Results.

2 or rfEnableErrorsOnly: Only those events with a fail status are displayed in the Test Results.

3 or rfDisableAll: All events in the Test Results are disabled.

ReportPath Property

This is used to get the path in which current test results are stored.

Its syntax:

Path_of_Results = Reporter.ReportPath

RunStatus Property

This is used to get the current status of the run session

Its syntax:

Reporter.RunStatus

For Example:

if Reporter.RunStatus = 0 then flag=1;

what is smart identification technique?