Thanks for the thoughts thus far - but, here's a new twist (and techgnome, this may be where you're going and I don't see it)...

Instead of wanting to actually store my non-collection objects in an array, I determined what I really need is to store a property in an array...

Here's what I mean..

This app is a User Mangement app for a Win2K AD structure.

I only want to update the particular user attributes that the client has changed, so for example.

txtPassword.Text = "NewPassword"
chkMustResetPassword.Value = 1

Then to set those I use an LDAP query to the IADsUser object, such as for example...

User.Password = NewPassword
User.MustReset = CStr(CBool(1))

What I would like to do is store in the array the User properties that have changed and their values. So again I figure I could key off the object's change event.

The question now is, can I store the changed "properties" in an array to be looped through when saving the changes, w/o having to resort to a large CaseSelect statement or something of that sort?

Thanks again for the help...
QuaffAPint