Is there any functional differences between the construct: Set CurRow = TblPersonalInfo.Rows(1) Set CellsColl = CurRow.Cells Set CurCell = CellsColl(0) and SetCurCell = TblPersonalInfo.Rows.Item(1).Cells.Item(0) ? Thanks
"JonWayn" wrote in message news:8B5512D6-9D06-4C6B-B5C2-B73146A033DF@microsoft.com > Is there any functional differences between the construct: > Set CurRow = TblPersonalInfo.Rows(1) > Set CellsColl = CurRow.Cells > Set CurCell = CellsColl(0) > and > SetCurCell = TblPersonalInfo.Rows.Item(1).Cells.Item(0) > ? No, not really. You can make it even shorter: Set CurCell = TblPersonalInfo.Rows(1).Cells(0) -- With best wishes, Igor Tandetnik With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925
I knew of that usage too: I tend to always use multiple statements thinking that referencing a closer relative might have had a more reliable connecton than for a more distant relative, and would be less proned to throwing those nasty 'Permission Denied' errors. Thanks for the insight. "Igor Tandetnik" wrote: > "JonWayn" wrote in message > news:8B5512D6-9D06-4C6B-B5C2-B73146A033DF@microsoft.com > > Is there any functional differences between the construct: > > Set CurRow = TblPersonalInfo.Rows(1) > > Set CellsColl = CurRow.Cells > > Set CurCell = CellsColl(0) > > and > > SetCurCell = TblPersonalInfo.Rows.Item(1).Cells.Item(0) > > ? > > No, not really. You can make it even shorter: > > Set CurCell = TblPersonalInfo.Rows(1).Cells(0) > > -- > With best wishes, > Igor Tandetnik > > With sufficient thrust, pigs fly just fine. However, this is not > necessarily a good idea. It is hard to be sure where they are going to > land, and it could be dangerous sitting under them as they fly > overhead. -- RFC 1925 > > >
