Hi All,

Just wondering if anyone had run into the problem of when you update a
column with VBA then all your VLookup and Match references pointing at
it become #REF.

Is there a way to stop this happening because its kind of annoying :/

Cheers again,
Sau


---
Message posted from http://www.ExcelForum.com/

Sau,

It sounds like you're overwriting some stuff, but you need to be more
specific.

Rob

"Sauron " wrote in message
...
Hi All,

Just wondering if anyone had run into the problem of when you update a
column with VBA then all your VLookup and Match references pointing at
it become #REF.

Is there a way to stop this happening because its kind of annoying :/

Cheers again,
Sau


---
Message posted from http://www.ExcelForum.com/

I'm copy-pasting over a table of info but the vlookups referring to th
area I'm pasting to don't like it and change their formulas to #Ref.

Cheers Guys,
Sa

--
Message posted from http://www.ExcelForum.com

Is there a way to 'lock' the vlookup formulas does anyone know?

Cheers,
Sau


---
Message posted from http://www.ExcelForum.com/

Any thoughts Rob?

:

--
Message posted from http://www.ExcelForum.com

I'm not Rob, but are you sure you're copying--not cutting, then pasting?

You may want to post that part of your code if this didn't help.


"Sauron <" wrote:

Any thoughts Rob?

:(

---
Message posted from http://www.ExcelForum.com/

--

Dave Peterson

Sauron,

I don't mean to ignore you. I only get a couple of hours each night to
answer questions.

I don't think locking the vlookup is the right option. Better to fix the
root cause.

I've done a few tests here and can't replicate your problem of #REF when
strictly overwriting.
The problem can occur if the column_offset_num is greater than the number of
columns in the table array.

Without looking at the code, I can't tell for sure what the problem is.

Rob


"Sauron " wrote in message
...
Any thoughts Rob?

:(


---
Message posted from http://www.ExcelForum.com/