Animl
10-02-2006, 03:01 PM
This may already be known, so disregard if so,..
I'm still testing to verify. So far I find this with input type objects (Input, Combo Boxes etc..) if you have two pages with same name and type objects, those objects can appear and be functional on another page containing same name and type objects.
i.e..
Page 1 contains "M_ComboBx"
Page 2 contains "M_ComboBx"
If Page 1 is loaded and you go to Page 2, Page 1 object "M_ComboBx" will also appear and be fully functional on Page 2. It will also and still make changes (if set to do so) on page 1 while you're viewing page 2.
I couldn't figure out why I was getting page 1 objects on other pages.
Since I copy & pasted a lot of content from page 1 to page 2 they had same names.
I have no idea what sparked the idea but I went into page 1 and renamed the object from M_Combobx to M1_ComboBx, and the problem went away.
I could be wrong about it beinf fixed but so far in 20 test it seemed to have fixed it.
Just FYI ;-)
I'm still testing to verify. So far I find this with input type objects (Input, Combo Boxes etc..) if you have two pages with same name and type objects, those objects can appear and be functional on another page containing same name and type objects.
i.e..
Page 1 contains "M_ComboBx"
Page 2 contains "M_ComboBx"
If Page 1 is loaded and you go to Page 2, Page 1 object "M_ComboBx" will also appear and be fully functional on Page 2. It will also and still make changes (if set to do so) on page 1 while you're viewing page 2.
I couldn't figure out why I was getting page 1 objects on other pages.
Since I copy & pasted a lot of content from page 1 to page 2 they had same names.
I have no idea what sparked the idea but I went into page 1 and renamed the object from M_Combobx to M1_ComboBx, and the problem went away.
I could be wrong about it beinf fixed but so far in 20 test it seemed to have fixed it.
Just FYI ;-)