On Sat, 4 Feb 2006 16:09:26 -0800, "GS"
wrote:
Thank You

This may be something to investigate. I do have macros in other
workbooks copying these named ranges. I will have to go back through
them to see if this is maybe the case. Maybe I need to even rethink
using DefineNames this way.
I do appreciate the point in a helpful direction

Scott


Hi Scott,

Defined Names can be a nightmare if they aren't managed properly. For
example, another user may be copying a sheet from another workbook that also
uses the same defined name ("June"). I find it safer to use local scope for
this because the names follow the worksheet. Unfortunately, so do global
names, and this can cause your previous defined name to change its .RefersTo
property depending on how the user answered the alert message during the copy
process. I didn't see a local scope in your description here but you might
want to modify things as follows:

Name: 'SheetName'!DefinedName
RefersTo: 'SheetName'!$Col$Row

To purge the global scope name, add a new sheet, then INSERTNAMESDEFINE,
then delete the global name from the list. Since this sheet is new it won't
have any local names listed, so all names you see in the list will be global.
Delete the sheet when you're done and save the file.