Re: why>?
- From: "aaron.kempf@xxxxxxxxx" <aaron.kempf@xxxxxxxxx>
- Date: 25 Jul 2006 20:10:19 -0700
those are by-revenue not by-seat
oracle users cost $149 minimum.. whereas sql server is-- for the most
part-- free-- and it has been for 7 years now.
free doesn't calculate into a revenue formula very well.
Oracle sucks balls; i've worked at small startups where it takes a half
dozen oracle dbas to have a simple ecommerce site.
half dozen dbas and a dozen developers?
for christ sakes; oracle is off by an order of magnitude.. they-- and i
quote-- suck balls compared to sql server in usability, performance and
stability.
and olap?
www.olapreport.com looks to me like MS has 5 times the marketshare of
oracle; at least that's the way I interpret the numbers.
you 'excel dorks' could have a decent future-- if you would learn MDX
en masse'
pardon the french --
then you might be able to USE some of your excel skillz for something
productive.
but you kids are fat and lazy; followed by more fat and lazy.
your company isn't an efficient company.. efficient companies have
efficient intranets and efficient internet sites.
the fact that you kids are stuck in excel is laughable; you are stuck
on the first rung of the technology ladder
kids grow some ballz and get some skillz
-Aaron
Harlan Grove wrote:
aaron.kempf@xxxxxxxxx wrote...
also; back in the 90s; it might have been a good idea to use Excel.
people were stupid back then and didn't have alternatives.
So you don't realize that Access was available back in the early 1990s,
though from 1992 or so. I used R:Base on PCs back then myself, and DB2
was on the mainframe.
now that SQL Server _OWNS_ the market; i'll be damned if you keep on
using Excel for every single app you write.
Then be damned. Your choice.
BTW, care to back up your statement. Take a look at
http://arstechnica.com/journals/microsoft.ars/2006/5/31/4163
which shows
"For 2005, IDC issued the following statistics pertaining to RDBMS
market share:
* Oracle: 44.6 percent
* IBM: 21.4 percent
* Microsoft: 16.8 percent
* Sybase: 3.5 percent
* Teradata: 2.9 percent"
Care to tell us how you define 'owns'?
Applications that are written in Excel are:
Generalizations. Are all first or second applications written by new
Access users perfect? But lets take this point by point.
a) inconsistent
In what way?
b) incomplete-- 'designing' in excel might be good for prototypes; but
nothing else
In what way?
c) not scalable
Fair point, but spreadsheet models are meant to be single user.
d) prone to data entry errors - since Excel doesn't have ANY data
validation capabilities
No more prone than databases. Data validation doesn't prevent all
mistakes. Data validation prevents mistakes like too few or many digits
in phone numbers or numbers outside of reasonable ranges. It *is*
possible to catch such errors in Excel. It's just harder to do so
because Microsoft has provided nothing but trivial data validation
facilities for Excel. That you don't know how to handle this in Excel
is not surprise since you have no clue how to use Excel and less
capacity for learning how.
e) a spawning place for malware and virus...
If MDB files became as widespread as XLS files, the same VBA
vulnerabilities in Excel would be there in the MDB files. MDB files may
not have Auto_Open macros like Excel has, but all it takes is using
udfs in queries, forms or reports to run malicious code. E.g., create a
module in an MDB file with the following.
Function foo()
Shell "c:\winnt\system32\cmd.exe /k echo you are fubar!"
foo = 0
End Function
Then add calls to foo() in various queries, forms and reports. Since
udfs called from queries, forms or reports can run VBA's Shell, they
can run any executable. And since they can also create arbitrary disk
files using VBA's Open, Write and Close statements, they can create
arbitrary malware files on the fly.
The only ways you could avoid such malicious code in MDB files are (1)
set macro security options high, just like in Excel, and (2) only use
Access to view tables in MDB files and nothing more.
.
- Follow-Ups:
- Re: why>?
- From: Harlan Grove
- Re: why>?
- References:
- Prev by Date: Comparing Column B to Column A
- Next by Date: Re: Comparing Column B to Column A
- Previous by thread: Re: why>?
- Next by thread: Re: why>?
- Index(es):
Relevant Pages
|
