DaniBoy
Registered User.
- Local time
- Today, 09:18
- Joined
- Nov 18, 2001
- Messages
- 174
Hello
Its me again!!!
I took an Access Database Class like 3 years ago, from what I remember we had to first Desing the database on paper. Now, the way we did it was finding out what the client need it and then writting down all fields that they would use, from there we decided what fields would create a table.
Now I bought the Access2000 Bible book to have more knowledge about Access. I decided to start from Chapter 6 "A Case study in Database Desing" just to refresh my memo. Well it goes through the seven-step methods for desing. The first thing is the overall system desing, this is where you find out what the client wants. But here it actualy goes directly to desingning a "Report" . Now am realy
. Why does it do that? How can you make a report with out making the tables?!!
Does this make any sence to all the experts here? Should I stick to my old method of creating the table first? or was I tought wrong?
how do you rate this book?
Does anyone know of a Great book about Access?
Thanks
DaniBoy
Its me again!!!
I took an Access Database Class like 3 years ago, from what I remember we had to first Desing the database on paper. Now, the way we did it was finding out what the client need it and then writting down all fields that they would use, from there we decided what fields would create a table.
Now I bought the Access2000 Bible book to have more knowledge about Access. I decided to start from Chapter 6 "A Case study in Database Desing" just to refresh my memo. Well it goes through the seven-step methods for desing. The first thing is the overall system desing, this is where you find out what the client wants. But here it actualy goes directly to desingning a "Report" . Now am realy
Does this make any sence to all the experts here? Should I stick to my old method of creating the table first? or was I tought wrong?
how do you rate this book?
Does anyone know of a Great book about Access?
Thanks
DaniBoy