That's cool Bob,
one of the very nice things about ageing
is non fixed attachment to things.
Whilst I would not care to accept your point,
I would not care to debate it either
The thing is, it does the job I ask of it, and delivers
pertinent info, beit a database or an oxymoron.
Best wishes, and Regards.
Rodney
| 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)
|
| | > 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.
| >
| >
| >
| >
|
|