database management

1) http://en.wikipedia.org/wiki/Main_Page

2) http://www.google.com

1) You don't have to deal with the number of files, the fields, the physical location

2) Two models: hierarchical and relational. Hierarchicals are the good old IBM DBOMP and DL1, relationals are for example DB2, ABADAS, SQL-variants

3) Try to read this: Rob - Coronel: Database systems, ISBN 0-7600-1090-0

4) It depends on the category of your system. SQL-variants almost cover the whole spectrum.

Wow. these questions are almost like, "I want to buy a car, what's the best one?"

There are many different relational databases to chose from. As a rule, relational db are much easier to work with than hierarchical since you can easily make changes on the fly.

The biggest considerations are how many users you will have, where they will be located, where the db will be located, and how big/many records you will be tracking.

For example, my small group (15 folks) uses a Microsoft Access database to track time, effort and progress spent on projects (currently about 200). It works for us in that we can tailor reporting easily. FoxPro would probably work as well, but our company had already bought Access. Our db is on a shared drive and we can all access it easily from our LAN.

There are other db designed for larger deployments, such as Oracle and SQL Server. In this case, you would need to consider the machine that will hold the db. These would also work better if users will access the db via the Internet.

Just a few thoughts. If you ask our friend, Mr. Google, he will be able to give you bunches of products, but you'll have to sit down an g through these recommendations to find the best fit for your organization.

1) It take 5 min to search through filing cabinet and 5 sec in a database.

2) Same as above

3) There are software to build database software according to the database structure and interface user specified.

4) Too many to name.

What is the 6 number for next lottery?

Pineapple