reserved names r1_, c1_?
reserved names r1_, c1_?
(OP)
When naming ranges, we of course can't use a single letter and number (For example a1), because that is indistuinguishable from a cell address.
So I always add an underscore after cell names like that. Works fine most of the time: a1_, b1_, d1_, e1_, etc are fine. a2_, b2_, d2_, e2_, etc are also fine.
I noticed that if I try to use r1_ or c1_, I get an error message "c1_ is not a valid name" and "r1_ is not a valid name". Likewise, excel doesn't like r2_ or c2_.
Does anyone know why these particular names are prohibited? r and c reminds me of row and column, but I have not idea why r1_ and c1_ would be reserved.
So I always add an underscore after cell names like that. Works fine most of the time: a1_, b1_, d1_, e1_, etc are fine. a2_, b2_, d2_, e2_, etc are also fine.
I noticed that if I try to use r1_ or c1_, I get an error message "c1_ is not a valid name" and "r1_ is not a valid name". Likewise, excel doesn't like r2_ or c2_.
Does anyone know why these particular names are prohibited? r and c reminds me of row and column, but I have not idea why r1_ and c1_ would be reserved.
=====================================
Eng-tips forums: The best place on the web for engineering discussions.





RE: reserved names r1_, c1_?
RE: reserved names r1_, c1_?
RE: reserved names r1_, c1_?
To be honest, you should be giving your named ranges more intuitive names. You can prefix rng (short for Range) and name them anything you like. E.g. in macros, rngRow is perfectly acceptable, as is strRow, etc. but Row will get you into trouble as it's an existing object.
RE: reserved names r1_, c1_?
R1_ and C2_ L3_ etc are very intuitive names to me when trying to simulate a circuit which is labelled in the same manner. I guess I'll go with Res1, Cap2, L3_.
=====================================
Eng-tips forums: The best place on the web for engineering discussions.