Yep, understandable. In my example that I posted earlier, I used the
Formula property, so as to not only account for the previous situations, but
also to account for a cell value that may have an empty string value, but is
not truly empty. Of course, if the user is using that column strictly as
data entry, then your method would work as well.
Sorry if it seems like I get knick picking spotting so many different
things, but then when you get use to working with people that hardly even
know how to turn on a computer as I do and need to do programming work just
for that group of people to use, you get use to looking for anything that
may go wrong. Doesn't mean I catch them all, but still quite a few of them.
A few flat out reject having to use the system other than what the company
forces them to use. Some use only what they have to, and know what it's
basically for, but don't understand computers. Some understand computers,
but has no desire to learn much. Some has the desire to learn some, but not
into the technical stuff. A minor few has actually wanted to learn the
technical stuff for their own use and I have been able to help them learn
along the way.
In the case of all cells with something in it, I just have the very last
cell selected. Unless they really have that much data entry happening, the
only way I can see that happening is if they have something that pulls in so
much information from another source that it could very easily lead to
overflowing issues, which I have seen with query add-in programs linked into
Excel.
Yeah, I look for whatever could possibly go wrong and/or give an unexpected
results. I don't know about you, but I don't like to have to go back out
and touch every single computer, even if it is only deleting modules and
then importing modules.
--
Thanks,
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000