View Single Post
 
Old 11-08-2013, 05:23 PM
macropod's Avatar
macropod macropod is offline Windows 7 32bit Office 2010 32bit
Administrator
 
Join Date: Dec 2010
Location: Canberra, Australia
Posts: 22,467
macropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond repute
Default

Quote:
Originally Posted by mikec View Post
Yes that works. I presume because your formula uses sheet references rather then table references.
Actually, it doesn't use either.
Quote:
I started using tables because they seemed to provide benefits over ranges such as auto formula change for columns, column sorting and such. I therefore have always tried to make my code use "table cells" as opposed to "sheet cells" which makes the code independent of any sheet position changes.
I've attempted to adapt your formula to reflect this policy but as soon as I try to use a table column reference [column name] the problem I descibed to you comes back.
I'm not sure what you mean when you refer to "table cells", named ranges, perhaps?
Quote:
One of the issues I don't understand is why a Range.Copy...Range.Paste does not cause formula curruption but row.select...listRows.Add...Paste does.
Both forms of data transfer work as predicted but for the formula changes. Do you think this is an Excel bug or am I missing something.
Without knowing which particular sub is causing problems, I can't say. I don't propose to go through all your code (you have 10 modules and 8 worksheets!) and test all the code in each one - especially when I don't know what you regard as the correct or corrupt output in each case.
__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]
Reply With Quote