Hello,
I have a client app written in c# that contains checklistbox. I had the statement clearselected() to clear out the checked checkboxes when the user loads the new case... Everything worked perfectly until my users got converted to new domain.
Since they got converted to the new domain, the checkbox is no longer cleared out on pageload. Whatever the user selected in the previous case remained checked for the new case. The problem is: the application will not do anything because there are nothing actually checked (the checkedindices collection is actually cleared)! The user either has to shutdown the app or manually uncheck/recheck the items in order to add them to the checkeditem collection.
The situation makes me thinking of the cache problem, but the data is brought back correctly for each case, excepts the checkboxes remained checked "graphically" on the UI. I had tried to clear the check marks of the checklistbox by looping through the checkedindice collection, but didn't help.
I have searched for a solution but did not see any. If anyone has suggestion please let me know.
Thank you very much in advance.
VN.
VickyPosted Nov 17, 2006, 7:57 PM
My app was build in .NET 1.1 (VS 2002), and the users have .NET 2.0 installed when they got converted. So, I had to compile my app in VS 2005. When running it in .NET 2.0, I had the same problem that the users did: checkboxes did not clear out. It looks like Microsoft has new command to clear the checkboxlist:
this.checkboxlist.SelectedItems.Clear();
The command this.checkboxlist.ClearSelected() seems no longer working for checkboxlist.
Thank you so much for replying to my post
VickyPosted Nov 9, 2006, 4:19 PM
Thanks so much for the advise. Yes, that's what I suspected too - it might be the new server's setting that affects the UI. To find out the differences between the two servers is quite difficult for me because it involves with the third party group and network group (the network group firmly said the two are identical!!! because they created an account for me in the image of the new domain, and the error did not happen when I tested the application with this test account ...
I will work with the network group to find the solution. But at the mean time, if anyone else out there has solution for this, please (pretty please) let me know.
Lots of thanks.
Guess GGuessPosted Nov 9, 2006, 4:07 AM
Try looking into the new domain on firewalling, protection, ect. Compair the new one to the old one and find out what differences there are. Many domain servers are similar, but it is rare you'll find a server that matches EXACTLY what the customer had before, expecially if the customer has not moved...if that is the case, be in close contact with your customer and ask for more information,
First night to this board, but I know many companies that provide for all in different areas...I just offer advise, for now, that may be helpful given your post here. Whether helpful or not, let me know though ok? I personally would rather see problems be solved sooner than later myself.