you need to optimize your sql queries.

Everything Is Possible!

To me, the query is not well optimized and I think, you should optimize your stored procedure. I have optimized the query and it may work for you: - WITH DuplicateRecords(Name,StreetAddress,City,State,ZipCode,Telephone,SecondaryPhone,AddressPK) AS ( SELECT T1.[Name],T1.[StreetAddress],T1.[City],T1.[State],T1.[ZipCode],T1.[Telephone],T1.[SecondaryPhone],COUNT(*) AS 'NoOfEntries',min(AddressPK) as 'AddressPK' from #Test1 GROUP BY T1.[Name],T1.[StreetAddress],T1.[City],T1.[State],T1.[ZipCode],T1.[Telephone],T1.[SecondaryPhone] HAVING COUNT(*) > 1 ORDER BY T1.[Name],T1.[StreetAddress],T1.[City],T1.[State],T1.[ZipCode],T1.[Telephone],T1.[SecondaryPhone] ) INSERT INTO tblLocalDataDuplicate ([AddressPK],[SlNo], [CategoryID],[ProjectID], [WebUrl],[Name],[StreetAddress],[City],[State],[ZipCode],[Telephone],[SecondaryPhone], [EmailID],[EnteredDate],[UpdatedDate],[UserId]) SELECT T1.[AddressPK],T1.[SlNo],T1.[CategoryID],T1.[ProjectID],T1.[WebUrl],T1.[Name],T1.[StreetAddress],T1.[City],T1.[State],T1.[ZipCode],T1.[Telephone],T1.[SecondaryPhone],T1.[EmailID],T1.[EnteredDate],T1.[UpdatedDate],T1.[UserId] FROM tblLocalData T1 INNER JOIN DuplicateRecords T2 ON T1.addresspk = T2.AddressPK --Delete the duplicate records DELETE tblLocalData WHERE addresspk IN(SELECT AddressPK FROM DuplicateRecords) please let me know when you are done. I hope this may help you. Regards, Suresh Dayma

Everything Is Possible!

please refer this link : - http://msdn.microsoft.com/en-us/library/ms972974.aspx[^]

Everything Is Possible!

yes, you are correct. you can store the sessions in the state server.

Everything Is Possible!

I will assign the viewstate to the property. Regards, Suresh Dayma

Everything Is Possible!

Aftab Sindhi wrote:

In short, problem is on 1st click, while subsequent clicks are working as expected.

Just Debug the code.

Everything Is Possible!

I really appreciate your help but i dont think this is a better solution. I would rather create a public property in the masterpage and cast the masterpage in all my content pages(there are around 40-50 pages). although it is a tedious work. I will store the id in the content page's viewstate.

Everything Is Possible!

I dont want to make changes in all the content pages because there are around 40-50 pages.It's tedious to incorporate this changes to all the files. Is there a way by which i have to modify only the master page?

Everything Is Possible!

but my id keeps on changing depending on the no. of tabs opened(Firefox). And Each tab has to maintain different ids(customerId for instance). Example I have a gridview having multiple customers. if i open multiple customer details on multiple tabs then there should be different customerid assigned to different pages. In case if i use cookie then it will store a single customerid and when the page makes a request then this id will be assigned to all the pages. I dont want to do like this. I dont think, this is a solution(i.e. Cookie)

Everything Is Possible!

No dear, it does not work.

Everything Is Possible!

Hi abhijit, is there any work around for this issue?

Everything Is Possible!

I dont think this is the solution.

Everything Is Possible!

I really appreciate your help. but still i have to make changes in all the content pages(i.e. globally) right. Isn't there way by which i have to make changes in the masterpage itself?

Everything Is Possible!

yes, you are correct

Everything Is Possible!

is there any workaround for this issue?

Everything Is Possible!

Currently, i have used the sessions to store this. but when the user tries to open it in a new tab then this does not work. Example I have a gridview having multiple customers. if i open multiple customer details on multiple tabs then it will overwrite the customer details. so it does not make sense to store customer details in Session.

Everything Is Possible!

Thanks for your reply. ok, just take an example this is what i want in masterpage, i have created a label called 'customer name'. and fetched the customer name from the database and assigned it to the label. when i navigate from one page to another then, I just want to retain the customer name across multiple pages without having to interact with the database. (Assume there is a single master page and multipe content pages.)

Everything Is Possible!

can we store viewstate in masterpage. so that when a user tries to open a new tab, the id is fetched from the viewstate.

Everything Is Possible!

Inherit DotNetNuke.Entities.Modules.PortalModuleBase in your user control class.

Everything Is Possible!

Try the below mentioned code:- function CallPrint(strid) { var prtContent = document.getElementById(strid); var WinPrint = window.open('','','letf=0,top=0,width=1,height=1,toolbar=0,scrollbars=0,status=0'); WinPrint.document.write(prtContent.innerHTML); WinPrint.document.close(); WinPrint.focus(); WinPrint.print(); WinPrint.close(); prtContent.innerHTML=strOldOne; }

..... ..... .....

:)