how to start with access 2007

[tintincute]

hi
there, i have a basic background of access 2007.

and i'm just wondering, what are you going to do first if your boss give you the database for study.

i mean what are the points that you need to look for and understand?

Thanks for your help

[DaveT]

The first thing I look at is the database schema (Database Tools, Relationships).

Is referential integrity set? Is the database normalized (one fact, one place)? What are the main tables? Does the table structure - overall - make sense?

Then I look at the content of the tables. How many records? How populated are the main tables (lots of blank fields? inconsistent data such as variations in spelling for what should be lookup fields - states, etc?).

Naming conventions - how are the tables and fields named? Are fields in different tables that hold the same data named the same?

Run a few queries on the data to get a sense what's really there.

Then I look for code (VBA) modules. If the app has no code modules it was probably not written by a developer (of course this is changing with Microsoft emphasizing internet-based apps for Access such as SharePoint and Azure where onloy macros are used).

Make a copy the app and run through it - navigation paths, add a few records here and there, edit/delete records. Look at the data source for the primary forms: are they single tables, queries, SQL statements?

Take a look at the reporting.

It helps if you can talk to the developer and get a sense of how the project came about.

Certainly talk the user community. Ask them how they use the app, what problems they know about, what new features they would like to see.

[ajetrumpet]

hi
there, i have a basic background of access 2007.

and i'm just wondering, what are you going to do first if your boss give you the database for study.

i mean what are the points that you need to look for and understand?

Thanks for your help

one thing you might want to consider is a book that covers what Dave has said. this will give you the theory you need. All databases are pretty much the same in theory, or built on the same principles rather, so study design and you'll understand the program pretty well.

I would say that if you want to know how to operate it, practice. There really is no other way to become an expert. It's just like studying for your degree in school. You can study for a lifetime and it'll never be the same as work experience. Just because someone is a walking encyclopedia doesn't mean they can make the magic happen.

E.g. - Just because you've studied Access for 10 years from reading books doesn't mean you can produce even the smallest sized database.

[weekend00]

Very good experience, DaveT.

My database has all problems you mentioned.
1 Different field names are used in different tables for same property. I tried to make them identical, but they did not like. So I just leave as is.

2 We put every thing in the main table, all long descriptions, not the code/id. and lots of fields are decided from other fields in the same table. In one sentense: this table has everything. The advantage is I can find everything in this one table, never need to create query using joins to find what I need.

[tintincute]

thanks so much for the info. I am not really sure if it was develop by someone, because the one who's in-charge gave me a demo today and first she let me download the template from the microsoft website, i.e. that "Customer Support Database" and then she told me that she edited the template to fit her needs.

So i downloaded that as well, and she wants me to study the logic of that template. But how can I study because when I downloaded it it was all empty. No information. But there are the list of the tables, forms, reports...

is there a note for this Customer Database support?

Thanks