Thanks for your reply, Actually, an id is what I have. Here is a snippet of code of what I have <form id="Form1" method="post" runat="server"> **<asp:textbox id="txtNumber"** _onkeyup="return txtQuoteNumber_onkeyup()"_ style="Z-INDEX: 101; LEFT: 24px; POSITION: absolute; TOP: 32px" runat="server" AutoPostBack="True"> </asp:textbox> **<asp:textbox id="txtFrmClient"** style="Z-INDEX: 104; LEFT: 400px; POSITION: absolute; TOP: 40px" runat="server"></asp:textbox> **<asp:textbox id="txtFrmServer"** style="Z-INDEX: 105; LEFT: 400px; POSITION: absolute; TOP: 80px" runat="server"></asp:textbox> **<asp:button** id="btnGet" style="Z-INDEX: 102; LEFT: 240px; POSITION: absolute; TOP: 32px" runat="server" Text="Get Quote"></asp:button> **<asp:datagrid** id="dgQuotes" style="Z-INDEX: 103; LEFT: 24px; POSITION: absolute; TOP: 88px" runat="server"></asp:datagrid> </form> now I also have function txtQuoteNumber_onkeyup() { //I want to be able to update one control from the other, for example txtFrmClient.value = txtQuoteNumber.value } Bsically I want to be able to update when another control gets updated, ultimately what I want to be able to do, is from the onkeyup function I want to force the grid to update Thanks for your help

Sri, If I'm understanding you correctly, your concern is with having to maintain two different releases. Meaning, your client will have version 1.0.0 at their site while you're working on the next release 2.x.x ... during this time, the client could encounter bugs/design flaws, which you'll have to fix in their build and make a point release (1.0.1) and you want a way to replicate that 'fix' into your 2.x.x code ... There is a way to do this using VSS, however, it is often times more complex than just cutting and pasting your fixed code between the two releases. VSS provides a means to "share" branched code between releases. If the code segment is not different between your branches, then your "replicate my fix between versions 1.0.1 and 2.x.x" would work. HOWEVER, if you've modified that code segment already for your 2.x.x release, then that segment is no longer 'shared' and you would have to manually copy your fix between releases. You can find more information on this concept in the VSS help system (look at Shared code and Branching); you may have to read the help installed on the VSS server, since I believe branching is an VSS Admin function ... (you'll have to figure this out yourself). It is my personal opinion, however, that it is far easier, and a better practice, to make your fix in your version 1.0.x code base and then manually copy that fix over to your 2.x.x build. When you turn your code over to your QA group, they should regression test all those 1.0.x point release fixes you made, in the newer 2.x.x build, to ensure they are indeed fixed. Doing this, also helps ensure that (1) the bug was actually fixed as thought and (2) that newer code introduced in your new build has not directly affected your previous fix (not that this would ever happen ...) :rolleyes: That's my two cents, D.