Would you care to enlighten me as to how I have mis-used oxymoron? As I
said, by my understanding a flat file is not a database, so the term flat
file database is an oxymoron.


"Jezebel" wrote in message
...
The fact that you don't understand flat file databases -- presumably you
weren't taught about them because they were already out-of-date -- doesn't
invalidate the concept. You just make yourself look silly making pompous
declarations on a topic that you admit you don't understand.

And you might be wise to look up 'oxymoron' before you embarrass yourself
any further.





"Bob Phillips" wrote in message
...
Hi Rodney,

I think that is my point. Excel is NOT a database, however hard many
people
try and make it (including MS in 12?), and a flat file is a flat file.
It
might be able to manage tasks that were originally done by flat files or
even databases, but it still is not one. A database as I was taught has
files/tables whatever, and a some form of structure. So to me, a flat
file
database is an oxymoron.

--
HTH

Bob Phillips

(remove nothere from email address if mailing direct)

"Rodney" wrote in message
...
G'day Bob,
Excel is a flat file database, when used as such,
as opposed to a "Relational Database, eg: Access

A flat file database is described by a very simple database model,
where all the information is stored in a plain text file, one database
record per line. Each record is divided into fields using delimiters or
at fixed column positions. The data is "flat", as in a sheet of paper,
as compared to a more complex model such as a relational database.

I use MSWorks for smaller files, but that will only take 32,000
records,
so for larger volume, I have to sneak over to Excel.
The benefits of MSWorks include a learning curve of about 10 minutes
to be up and running, and for small jobs, like organising Local Cricket
database, record collections, and so forth.
HTH





| What is a flat file database? Sounds like a contradiction to me.