correct procedures to use access

  • Thread starter Thread starter bluebean
  • Start date Start date
B

bluebean

I know basically you can start with creating a database > by create tables,
then create query , then Form, then report.

But can I know that what is the correct process or procedures to from
starting to the end of a database project?

I still dont know about the overall concept about access. Can I know that any
information or examples which teach people from start to completing a
database project?

many thanks
 
Hi

Open access and press F1 and search "Getting to know Access". This will
open an audio course from microsoft. This is as good a place to start as any
I know.

Good luck with your project.
 
Database design philosophy varies with database developers, and even from
project to project by the same developer. You basically have the design
order correct, but sometimes you need to work backwards.

For instance, suppose there are a bunch of paper forms with the data. We
must use the forms as a source for designing the tables. The same holds true
if there are final reports. We must design the tables so that the finished
reports will contain the same data as the paper reports.

Sometimes, the data exists as dozens (or more) of spreadsheets, and we have
to make sense out of a relational design based on them. The point is: there
is no specific path of design that always holds true.
--
Arvin Meyer, MCP, MVP
Free MS-Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
 
ya arvin thanks.. becoz i have thinking to work backwards, but i m afraid i m
wrong so i wondering how to start. :)
Database design philosophy varies with database developers, and even from
project to project by the same developer. You basically have the design
order correct, but sometimes you need to work backwards.

For instance, suppose there are a bunch of paper forms with the data. We
must use the forms as a source for designing the tables. The same holds true
if there are final reports. We must design the tables so that the finished
reports will contain the same data as the paper reports.

Sometimes, the data exists as dozens (or more) of spreadsheets, and we have
to make sense out of a relational design based on them. The point is: there
is no specific path of design that always holds true.
I know basically you can start with creating a database > by create tables,
then create query , then Form, then report.
Click to expand...
[quoted text clipped - 8 lines]
many thanks
Click to expand...
Click to expand...
 
Draw it out on paper. Once you know the data requirements, you need to
sketch out the table structure. Say you know that you need to record
multiple phone numbers. That should tell you that you need a table of phone,
FAX, and cell numbers and perhaps email addresses. It should also yell you
that you need a PersonID field to link to the people table, and a TypeID to
link to a table telling you what type of number it is. Draw it all out and
then finalize each table.
--
Arvin Meyer, MCP, MVP
Free MS-Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

bluebean via AccessMonster.com said:
ya arvin thanks.. becoz i have thinking to work backwards, but i m afraid
i m
wrong so i wondering how to start. :)
Database design philosophy varies with database developers, and even from
project to project by the same developer. You basically have the design
order correct, but sometimes you need to work backwards.

For instance, suppose there are a bunch of paper forms with the data. We
must use the forms as a source for designing the tables. The same holds
true
if there are final reports. We must design the tables so that the finished
reports will contain the same data as the paper reports.

Sometimes, the data exists as dozens (or more) of spreadsheets, and we
have
to make sense out of a relational design based on them. The point is:
there
is no specific path of design that always holds true.
I know basically you can start with creating a database > by create
tables,
then create query , then Form, then report.
Click to expand...
[quoted text clipped - 8 lines]
many thanks
Click to expand...
Click to expand...
Click to expand...
 
ya, have have done that.. Now i can start entering record using a form, and
they seem work well.
I m able to link all the related tables :) Thanks

Now i need to put effort on how to extract information from these records. :)

Draw it out on paper. Once you know the data requirements, you need to
sketch out the table structure. Say you know that you need to record
multiple phone numbers. That should tell you that you need a table of phone,
FAX, and cell numbers and perhaps email addresses. It should also yell you
that you need a PersonID field to link to the people table, and a TypeID to
link to a table telling you what type of number it is. Draw it all out and
then finalize each table.
ya arvin thanks.. becoz i have thinking to work backwards, but i m afraid
i m
Click to expand...
[quoted text clipped - 21 lines]
Click to expand...
 
Back
Top