Excel 2002 - Can this be done?

[M Henderson]

Does anyone know if this is possible?

I have a worksheet in which I enter commission-related
information for our salespeople. The worksheet computes
the commission due each sales person. After computing
the commission I print the report, and then I use the
same worksheet for the next salesperson. I then go to a
separate worksheet (a different worksheet assigned to
each salesperson) in which I enter much of the same
information for our record keeping. Is it possible to
set up a macro that will grab the information from the
first worksheet, input the information on the second
worksheet based on the appropriate sales person, and then
move the cursor to the first cell in the next row so it
is ready for input from the next commission calculation?

Thanks a lot!

 

[Don Guillett]

Excel can do almost anything.

Set up a macro that prints the data inputed and then moves to the
appropriate salesperson and clears the report.

OR

Enter the info in the persons ws and have a macro that prints loops through
the worksheets to get the data and prints all reports at once while you take
a nap.

 

[Bob Phillips]

Excel can do almost anything.

But that doesn't mean that we should try to make it do so. It's not a
database, it's not word-processor, it is not a project planning tool, and it
is not a presentation tool, but we have all seen each of those tasks forced
into Excel.

Bob

 

[Don Guillett]

IMHO

It's a great small database and not a bad word processor.

For instance, I recently had a customer that wanted some legal forms filled
in from a master sheet where you put in: name,address, legal, price,
etc.etc. and have the same info goto about 15 sheets of legal size
documents. I did the whole thing in Excel. I also have a small property
owners association that I designed a program for that does a variety of
customized letters that fills in the blanks depending on a "x" in a column
using a for each loop that sends an email to those that have an email
address and a letter and envelope to those w/o and email address.

I also designed some point of sale software for insurance agents using the
same concept as the 1st one mentioned here. The agent fills in the data
about the client and excel creates a presentation that takes them one tab at
a time. No PowerPoint needed. It has 7 graphs etc. and all the agent needs
is Excel. The bad is that many of them only have xl95 so I design there and
test in 97 and xl2002. I get paid an ungodly sum each year just to update
the tables which include military pay , benefits, and social security
figures. I sometimes make minor changes based on changes in the benefits
available to the military.

I recently did a small one for a rental agency to send out monthly invoices
to their clients. One mouse click.

I like Excel.

 

[Bob Phillips]

Don,

Sorry, but in my view it is not a database, and it's a terrible
word-processor.

It sounds to me as though you like it because of some previous bad uses of
the tool keep you in revenue<vbg>.

I know it can be made to do many things, but my point is that we shouldn't
do it if it's the wrong tool. Like those millions of Excel Gantt charts ,
loads of code and function to support something that other products do
better. Where I work we have a reporting tool called Brio. Brio retrieves
data from many sources and can process that data and format in tables,
charts and/.or pivots. It's a great tool, but most of the users download the
pivots into Excel to view it there. They do nothing with it that couldn't be
done in Brio, but they still insist on doing. By perpetuating Spanish
practices like these we are costing our companies a fortune.

And I like Excel too, just look at how long I spend here, and I am guilty of
these mistakes myself, but I do try to keep reminding myself.

Regards

Bob

 

[Harlan Grove]

Sorry, but in my view it is not a database, and it's a terrible
word-processor.

Butting in.

It's an adequate list processor for modest tasks. It ain't a transaction-based
relational database or even an adequate flat-file database. (I'll admit I'm
spoiled by what 123 provides, and Excel is simply pathetic in comparison.)

Text boxes are better than worksheet cells for simple text entry. As for 'word
processors', it kinda depends on definitions, which means which features are
necessary and which superfluous.

Still, these (mis)uses don't bug me anywhere near as much as using Excel for
system administration tasks. Manage your network from Excel at your own risk!

It all boils down to the age old problem: most people confronted with the need
to drive a screw and having a hammer at hand while the drill and screw driver
are down the hall will choose the path of expedience.