Re: Vlookup nightmare

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

aaron.kempf@xxxxxxxxx wrote...
>excel can NOT
>
>excel can _NOT_ do loops like SQL can.
>
>SQL Server can loop through using a cursor.

Procedural code can loop through a cursor into a dbms table. SQL
queries don't. Another BFD! Procedural code can loop through
spread*** cells. Equally a BFD! NO DIFFERENCE!

Apparently you define 'Access' to include any & every additional tool,
add-in, scripting language, or other software you find useful when
using Access/SQL Server/MSDE/whatever, but you define 'Excel' as only
what's provided in worksheets without even any VBA.

So much for a fair comparison. No wonder your perspective on the two
programs is so skewed.

>MSDE is a freeware version of SQL Server; and it is included with
>Access. This is much better

Fine. As long as one has MSFT Office Professional (or Enterprise?), one
has both Access and MSDE. But for those not so few who have MSFT Office
Standard, they have *NEITHER* . . . but they do have Excel.

Excel **ALWAYS** comes with every version of Office. Not so
Access/MSDE.

>Excel is too buggy; i mean-- this whole Office Suite-- it just doesnt
>work well enough to be sold and I want a refund for every employer i've
>ever been at.

Read the EULA. MSFT disclaims the software is useful for anything.
People use it at their own risk, at their own whim, and for whatever
benefits they hope to derive from it, but MSFT has *NO* obligation to
make it useful or make it work the way you seem to want it to.

There are bugs in Excel, but you mean documented functionality for
which you haven't bothered to read the documentation or are too stupid
to understand.

.

Quantcast