I wasn't orginally using a project reference, just a normal binary reference. But that does seem to have fixed it. Thanks.

Good grief man! That's beautiful. :-o Thanks < bows down as he backs away slowly >

If you have a application config file, make sure that you're not explicitly setting the codebase for dependent assemblies. Otherwise, you're .NET installation is screwed up. Dependency resolution first checks the current and private paths (like the bin folder in ASP.NET applications), then it looks in the GAC for assemblies. One you thing you could do to see why the bindings aren't occurring is to start fuslogvw.exe, make sure logging is turned on, then start your application. Refresh fuslogvw and see what it says. If it states something about not being able to find the localized resources for your default locale (like mine is "en-US"), you can either ignore these - or to make your assembly resolution faster, add the assembly-level attribute assembly: System.Globalization.NeutralResourcesLanguage("en-US"); (with the appropriate locale). For each binding error, it will show you everywhere it attempted to look which might help you resolve the problem. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

........and the solution is.....................pass your controls around by reference and not by value....ta da!!

Problem sorted - it was down to dumb user error :-(

I originally compiled it on framework 1.0, and the subsequent tests were run on 1.0, 1.0 SP1, 1.0 SP2 and 1.1, with varying OS's. I have just now compiled it on framework 1.1, and it works fine on my dev machines (I didn't send it out for beta testing again). Just to be clear, what should be happening is that any text located in textBox1 should be copied to each TexBox in the collection when button1 is clicked. Like I noted previously, I have coded far deeper references than this that are in production systems, without problems. Maybe there's a problem with the way your system/s are compiling the code? I know that's a bizarre scenario, but this is a bizarre behavior! I you like, I can send you a compliled version for testing, just send me an email address to use.

Thanks for your suggestion, but unfortunately the references are still lost, and it would appear when the control and object are passed into the collection, they are passed copies. Sorry for leading you up the garden path by using that .Clone(), I was experimenting in the code - needless to say that didn't work. Anyhows, have implemented exactly what you specified, and the behaviour suggests that you cannot have a reference to a reference!!! In the good old days when I were but a young lad, and sweets were a penny each, and mobile phones were the size of a house, I could just use StrPtr(), but this feature has been ripped out of .NET...........:-(