Working with groups of user controls...

I have nineteen user controls that are named "user_" concatenated with
(0-18). How can I loop through and set the visibility property to false for
each one. I tried something like:
protected alss.controls.something user_0;
protected alss.controls.something user_1;
protected alss.controls.something user_2;
...
for (Int32 i = 0; i <= 18; i ++) {
UserControl objUser = (UserControl) Page.FindControl ("user_" + i.ToString);
objUser.Visibility = false;
}
Any ideas?That didn't work?
MY ASP.Net tutorials
http://www.openmymind.net/
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:8EFD1FB2-6EC4-4BA3-9FD4-61E20A1DBCBF@.microsoft.com...
> I have nineteen user controls that are named "user_" concatenated with
> (0-18). How can I loop through and set the visibility property to false
for
> each one. I tried something like:
> protected alss.controls.something user_0;
> protected alss.controls.something user_1;
> protected alss.controls.something user_2;
> ...
> for (Int32 i = 0; i <= 18; i ++) {
> UserControl objUser = (UserControl) Page.FindControl ("user_" +
i.ToString);
> objUser.Visibility = false;
> }
> Any ideas?
Nope
"Jim" wrote:

> I have nineteen user controls that are named "user_" concatenated with
> (0-18). How can I loop through and set the visibility property to false f
or
> each one. I tried something like:
> protected alss.controls.something user_0;
> protected alss.controls.something user_1;
> protected alss.controls.something user_2;
> ...
> for (Int32 i = 0; i <= 18; i ++) {
> UserControl objUser = (UserControl) Page.FindControl ("user_" + i.ToString
);
> objUser.Visibility = false;
> }
> Any ideas?
Could you be more vague and provide less details?
did it throw an exception or simply not make things hidden? Maybe you can
give us more code? clearly that isn't it since it'sVisible and not
Visibility...
Karl
MY ASP.Net tutorials
http://www.openmymind.net/
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:B235A7DE-D6FE-48FF-B9F2-F921FE4208D1@.microsoft.com...
> Nope
> "Jim" wrote:
>
for
i.ToString);