Hi Wicked. Yes I used Offset based formula to define my named ranges.

GS: What you suggest is to use code to hard define a named range then
access that range via a database connectivity tool to then try and
set a data validation list by code assuming it will fit in the 255
character limit. This would require different code for each dynamic
validation. Or I could just use a database and handle it in a
properly controlled way. I am always amazed at people trying to force
poor fit methods into excel attempting something handled far better
by other tools. This is a case in point. You could probably force the
data into something excel might be able to work with, involving
either a lot of human effort or cobbled code making it hard to
support, or do it in a standardized and supportable way with a
database. I appreciate your help with this but it turns out that
excel is a poor choice to solve this.

No.., that's not the context of what I'm suggesting.

I suspect your opinion that Excel is a poor choice to solve this is
based on your level of skill with using Excel as a database management
solution compared with your level of skill with Access. I do in Excel
exactly what you're trying to do here as a matter of common tasking,
based on my level of skill using Excel compared to near zero level of
skill using Access. Whenever my tasks require a real database I use
SQLite when needs exceed the capabilities of text files or
spreadsheets.

IMO, it shouldn't matter what format (mdb, dat/txt, xls) your database
is since ADODB handles recordsets pretty much the same way for all. The
'catch' is in how to structure the database. Where Excel or text files
are used, new data gets added/removed 'dynamically' into its respected
fields/records/tables.<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion