A
Aminoplacid
Hi,
I had been working on a highly customized .NET 1.1 datagrid for a
project with lots of javascript iterating through my datagrid. I had
installed .NET 2.0 a while back and no problems. I had installed SQL
Server Management Studio: no problems. I had just installed Visual
Studio 2005 yesterday (for Reporting Services) and now when I run my
application (from VS 2003), the datagrid numbering format is all
screwy. For rows 1-9, the format was
[datagridid]__ctl[rownum]_[itemid]. Now it is
[datagridid]__ctl0[rownum]_[itemid]. For example,
grdDataGrd__ctl2_ItemName is now grdDataGrd__ctl02_ItemName.
I had installed my app on my managers laptop (2 weeks prior) and got
the same behavior, too.
Any ideas why this is? What can I do short of rewriting all my
javascript to accomodate this? Anyone else come across this?
Thanks for the ideas.
Derek Baker
I had been working on a highly customized .NET 1.1 datagrid for a
project with lots of javascript iterating through my datagrid. I had
installed .NET 2.0 a while back and no problems. I had installed SQL
Server Management Studio: no problems. I had just installed Visual
Studio 2005 yesterday (for Reporting Services) and now when I run my
application (from VS 2003), the datagrid numbering format is all
screwy. For rows 1-9, the format was
[datagridid]__ctl[rownum]_[itemid]. Now it is
[datagridid]__ctl0[rownum]_[itemid]. For example,
grdDataGrd__ctl2_ItemName is now grdDataGrd__ctl02_ItemName.
I had installed my app on my managers laptop (2 weeks prior) and got
the same behavior, too.
Any ideas why this is? What can I do short of rewriting all my
javascript to accomodate this? Anyone else come across this?
Thanks for the ideas.
Derek Baker