Using Range to refer to cells

I'm a bit confused. I have a custom function that works perfectly when I use the following to set the range I'm working with.

Please Login or Register  to view this content.

As part of an ongoing development I'd like to be able to pass the name of the range in the function, but before I get there I needed to make sure I had the syntax right for changing the specfic range above to a set of named cells. The cells above are called "Table_0" and this applies from anywhere in the workbook, so why does the following code not seem to work?

Please Login or Register  to view this content.

Rather than an answer it just gives me a #VALUE error. WHat am I missing?

Well that was staring me in the face! That works perfectly. Thanks. Even managed to butcher it to take the range as a variable- which it turns out was a lot easier! If there are two workbooks open with the same named range does that cause an issue? Or will it always just look at the activeworkbook?

Does that mean it will look for the same table in another workbook? If so is it as simple as changing it to false to stop it looking?

It's a table - from external data. Works as is simply enough thankfully. If I could avoid getting sheet specific that would be great (needs replicated across 40+ different workbooks). The joys!

In a VBA module in each of the workbooks. As I don't have control over where each one ends up (or how many copies) it's about the best I can come up with.

So I can simply make it "thisWorkbook.range("name here")" ? COulnd't get it going with thisworkbook before - but that's when I couldn't get it going at all of course!

That would answer why I had a problem then.

It may not be an issue but I can see a case where someone ahs 2 workbooks open at the same time. IN theory they will be looking at the same info regardless of which table they look at.

The workbooks differ in size. Some with one or two sheets some with about 20. Most will only have 1 table (and this should be the same table coming from the same external data) but one or two wil have secondary tables (which will have different names).