Re: The best elegant solution to override 65k rows limit in a ***
- From: "aaron.kempf@xxxxxxxxx" <aaron.kempf@xxxxxxxxx>
- Date: 6 Jul 2005 10:55:14 -0700
just for the record, ACCESS shouldn't be a product of your IT
department. It is a LOT more fun that Excel.. since you can make a
report and print if weekly; instead of make a report and make it
weekly.
I mean-- it's like the 20th century instead of the 18th century (using
Excel).
(Just for the record, I claim that Analysis Services, MDX, etc is 21st
century technology even though they shipped with SQL 7 in ~98-ish)
Access isn't that difficult.
Learn to write queries-- If you cant do it; then quit your excel job
and go to work at McDonalds. 8 years ago, I worked as a tester; and 30
of us testers were taught how to write Access queries in an hour.
I mean seriously-- with a couple of queries; a couple of macros and a
little bit of time-- there ins't anything in the world that you can't
calculate with Microsoft access.
I know that it's quite easy to learn. Just take baby steps and don't
get frustrated.
If you _REALLLLLLLLLLLLLLLLLLLLLLLLLLY_ want to process more than 64k
rows in Excel; you can actually use the Office Web Componenets
Spread*** control; I think that it is about 60% of the functionality
of Excel; but it actually has a limit of like ~250,000 rows.
You'd have to do some programming (VB is fun for the whole family.. i
mean... PERL??? wtf this is excel and access not rocket science)..
.
- Follow-Ups:
- Re: The best elegant solution to override 65k rows limit in a ***
- From: Harlan Grove
- Re: The best elegant solution to override 65k rows limit in a ***
- References:
- Prev by Date: Re: days between dates
- Next by Date: Re: Preserve Formatting
- Previous by thread: Re: The best elegant solution to override 65k rows limit in a ***
- Next by thread: Re: The best elegant solution to override 65k rows limit in a ***
- Index(es):
Loading