AssociatedControlID in ASP.NET--For in HTML

Once Click Label Control,Focus move to other control without use TabIndex property in ASP.NET

<asp:Label ID="lblName" runat="server" AssociatedControlID="txtName" Text="Enter Name"></asp:Label>
<asp:TextBox ID="txtName" runat="server"></asp:TextBox>

In the above code,lblName is associated to the TextBox "txtName". When executed and the focus will be returned to the TextBox if we click on the label text "Enter your Name".

In HTML
<label for="txtName" id="Label1">Enter your Name</label>
<input name="txtName" type="text" id="txtName" />

Set Link for Email Sending using javascript

javascript:location.href='mailto:?SUBJECT='+document.title+'&BODY='+escape(location.href);

Find time Elapsed In .net without using Timer Control

System.Diagnostics.Stopwatch calcElap= new System.Diagnostics.Stopwatch();
calcElap.Start();

//do my stuff
...

calcElap.Stop();
Response.Write("Time Elapse: " + calcElap.Elapsed.ToString());

SAP Exchange Infrastructure - Points to Remember (Part X)

(contd....)

66. Send step with in a block with ParForEach: the elments of multiline container element are processed in parellel instances of the block at runtime. If the send step within the ParForEach sends a separate message to be received for this message for each element of the multiline container, then send step can activate the corresponding correlation.

67. Abstarct/Message interface can be cretaed from MessageType/IDOC/RFC

68. An integration Process can use all the objects available in the Software Component Version SWCV

69. Loop step in a while loop, loops while the condition is true

70. The outermost block of a process is the process itself

71. Contaner elements defined in the Process Container are visisble in all the blocks, as this is the super block for all the blocks

72. A correlation can be activated either from a Send step or from a Receive step

SAP Exchange Infrastructure - Points to Remember (Part VIII)

(contd....)

61. Receive step to start the process can be the first step of the process or a block or a fork, or a loop. In either case the later fork,block, or loop must be the first step in the process

62. If a message comes, for which there is no waiting receive step then it is received by the process and and stored temporarily

63. The Synchronous Receive step( Receive step which opens sync/async bridge) must be the first step in the Integration Process

64. You can use only one Receive step to open sync/asyn bridge for each Integration Process. This receive step must start the integration process. There must be no other receive steps to start the Integartion Process

65. The Synchronous Receive step can be inserted in the following places
-->Directly after start marker
-->As the first step in a block, if the block is the first step of the Integration Process and has the mode standard
-->As the first step in the fork. If the fork already contains some starting recevie steps, the start process indicator is automatically reset for these steps.