I thought of typing that, and figured that someone would probably come back on it if I didn't.
But, I feel either way is sufficient.
My point was more the use of the banger.
What MS is referring to is the danger that a default property
may change in the future.
I do not see this happening with ADO under VB6.
And, Fields is a collection, so "Item" should always be the default.
Using "Fields", and the property "Value", on the other hand, (instead of just x = rs("SomeField"

), I think this is good practice.
The Item property is about the only property I leave out anymore.
However, when you one day find that defaults are not used anymore (already the case), as opposed to the problem with changing defaults, then you will need to get into other habits, of coding with-out defaults.
Actually, you could just use the faster Collect method:
rs.Collect("SomeField"
No defaults used here.