Why not just put whatever you're using as the range name into a column and use .Find() to locate the row?
--
Tim Williams
Palo Alto, CA


wrote in message ups.com...
Explain this "primarykey" to me because as far as I am concerned its
only good for refrencing the VLookup code and not for submitting data
to worksheet...

keepITcool wrote:
Never underestimate "the People" :)

I would not use Names for every record in a database.
Using names will give you (and Excel) way!!! too much overhead.

The Names collection just isn't fast/good enough with 10000+ members.
Also I've seen plenty of corrupted workbooks where NAME objects were
the cause.

I'd create a "primaryKey" column in the database and fill that
with a unique (non editable) number for "pinpointing".


--
keepITcool
| www.XLsupport.com | keepITcool chello nl | amsterdam


wrote in
oups.com

Using names allows for my macros to pin point specific information and
pull the information and allow for it to edited and resubmitted to the
same area it came from...I don't understand why this is so confusing
for people...I guess not many people have attempted to write full
blown programs like this before in Excel?