Re: why>?


and the problem with your IF THEN IF THEN BULL***

is that it is limited in funcitonality.

IF CELL 1A = 'HELLO WORLD' THEN GIVE ME A WARNIGN THAT SAYS 'YOU MEAN
GOODBYE WORLD?'

your simple IF, THEN bull*** is laughable.



oh; but i can only nest this logic 7 levels deep!!!


fucking hogwash buddy.


get a real program with real events and real validation.

grow some balls and stop taking it in the ass.



Harlan Grove wrote:
aaron.kempf@xxxxxxxxx wrote...
I disagree.

Of course you do.

if you spend an hour a week inside of excel you should be classified as
a 'software developer' and you should be held to the same standards of
excellence as real developers.

Fine. When you hire Excel 'developers' for your own company, you can
institute this policy. Meanwhile, the rational people at all other
companies will continue to exercise the common sense which you find so
elusive and abstain from using a 'pregnancy' standard for software
developer positions.

you should have to use visual source safe.

Why not CVS?

Or is this another example of database = SQL Server, i.e., version
control = VSS?

You do have trouble with options.

you should have to have 9 different managers
...

?

That'd be efficient, if taken simplistically, which is the only way you
could have meant it.

with excel it is impossible to ensure datatypes.

You mean two things. First, it's difficult to enforce validation in
Excel. Agreed. It requires programming. Data > Validation is at best a
toy feature, easily broken or bypassed in the real world. Much like
Excel's internal passwords.

Second, you're whining because Excel shares the capability of nearly
all scripting languages of being able to store data of any type in any
cell. If you can't figure out that you need to check your data for data
type inconsitencies before trying to bring it into your database, do
you really know what you're doing?

More likely you're just whining about having to do so. Welcome to the
real world in which any group of 10 users can be expected to surface 12
or more unexpected design or implementation errors, in this case,
failure on the part of whoever designed the spread*** in question to
spread error values far & wide in the spread*** whenever ANY entries
were invalid. Nothing gives a user a wake-up call as efficiently as a
formula error message like

=IF(ISNUMBER(ExpectedNumericEntry),"","You have made an invalid entry
in cell "&
CELL("Address",ExpectedNumericEntry)&". This model maintains statistics
on invalid
entries and mails periodic efficiency reports to your manager and HR.
Please correct this
and be more careful in the future.")

I've never used this particular error message, but I've used similar,
shorter ones, and I once implemented e-mail notification to the user's
manager with cc to the user when they've tried to print or save with
invalid data. Printing disalllowed (other than screen prints), saving
permitted, but the workbook sent another e-mail about the need to fix
invalid entries upon reopening. I was not popular.

Yes, this requires programming, but if you or people you work for are
foolish enough to use Excel as a multiple user data entry front-end,
you need to implement the necessary validation controls. It may not be
easy, but it *CAN* be done, at least by people who know what they're
doing in spreadsheets.

.